Configuration and knowledge
- A company configures itself end to end without an engineer: name, products, prices, working hours, response promise, sales pipeline and stage meanings, where conclusions are written back, and the phrases its own customers use.
- Every price and product statement is approved word for word before RAJEH may say it — and editing the wording withdraws the approval automatically.
- Company knowledge is created, approved, corrected and removed by the customer. Correcting approved wording supersedes it rather than overwriting it, so the record of what was agreed survives.
- What the customer saves is what the runtime reads: working hours and response promises become the reply cycle; their customers' phrases become how RAJEH recognises intent.
Operating
- Customers waiting past the company's own declared response promise are detected, and the issue is given to a named person.
- Arriving leads are assigned by a rotation the customer chose by name. Choosing nobody refuses rather than inventing an assignee.
- Conclusions are written back into the company's own contact records, as tags. Not into named custom fields — that is stated as an exclusion on the page about what we do not claim, and the two pages must not disagree about the same fact.
- Contracted revenue is reconciled against collected revenue from the company's own invoices and payments.
Separation and safety
- One customer's data is never rendered or written under another customer's session.
- A person who belongs to several companies chooses which one they are working on; the system scopes to that choice rather than guessing.
- Every change to a company's governed configuration records what changed it, for which company, and when.