Law & accounting firms
Templates, fee schedules and document checklists change often. An answer given on the phone follows the version in force rather than a printed copy.
Your receptionist answers from your own documents, in their current version, and says where the answer came from.
7 days, 20 answered calls, no card
A base already answers everyday questions from content approved at configuration: hours, services, area, what a business does and what it declines. That carries far. Then comes the moment where the real answer sits in a document updated every season, one nobody copied over.
This add-on connects internal document collections. It follows their versions, inherits their permissions, applies removals, and answers by naming the document and version behind it. Somebody without access to a document does not receive its content in summary either.
Your documents do not carry live state. Stock, a balance or a schedule are read in the software that keeps them current, rather than in a copy of your documents: that is a design choice.
You authorise a private source and pick which collections should feed answers. Scope is explicit: whatever is unchosen stays unindexed.
A first index is built once. After that, only additions, replacements and edits are processed. Reconnecting a source does not restart that import.
Document rights are inherited and removals propagate. A permission change or a deletion does not rerun the document’s analysis.
An answer names its source. A sensitive rule change — a price, a condition — waits on validation before entering answers.
Frequently asked questions and initial configuration documents stay inside a base. This add-on brings the connection to private collections, version tracking and inherited access.
It respects the permissions of whichever software the document came from.
Templates, fee schedules and document checklists change often. An answer given on the phone follows the version in force rather than a printed copy.
Product sheets, warranties and site conditions live in your folders. A receptionist can point to them without inventing a technical value.
Administrative instructions from a practice — preparation, documents to bring, cancellation rules — are answered from your document, rather than from a generality about the field.
You choose the collections and approve sensitive rule changes. Nothing new enters answers without that step.
The add-on carries its own monthly volume, which you follow in your app, and it can be tried during the free trial.
Extraction already performed by another add-on is reused: indexing a document does not analyse it a second time.
With no source connected, your base answers from content you approved.
It does: hours, services, area, what you do and what you decline come from content you approved at configuration, and frequently asked questions stay inside the base. This add-on brings the connection to private collections, version tracking and inherited access.
No. You authorise a private source and pick which collections should feed answers. Scope is explicit: whatever is unchosen stays unindexed.
No. Document rights are inherited from the source and removals propagate: somebody without access to a document does not receive its content in summary either.
No. Your documents do not carry live state: stock, a balance or a schedule are read in the software that keeps them current, rather than in a copy of your documents. That is a design choice.
No. A first index is built once; after that, only additions, replacements and edits are processed. The same file is not counted twice, and a permission change or a deletion does not rerun the analysis.
What a base already answers, or how to assemble your own rules.
Your business data