Legal and accounting
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.
A document index is no source of live state. Stock, a balance or a schedule are read in their operating system, rather than in an indexed copy — this function claims nothing else, and that limit is deliberate.
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 triggers no new billed 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.
What it does not do: cleaning data, migrating history, or having a Zenvox team maintain a library. It does not bypass the permissions of whichever editor 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.
This add-on meters indexed pages, changed pages per period, private source accounts and collections.
Extraction already performed by another add-on is reused: indexing a document restarts no analysis charge.
A status shown is technical qualification. With no source connected, a 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. A document index is no source of live state: stock, a balance or a schedule are read in their operating system, rather than in an indexed copy. That limit is deliberate.
No. A first index is built once; after that, only additions, replacements and edits are processed. Content and version are deduplicated, and a permission change or a deletion triggers no new billed analysis.
What a base already answers, or how to assemble your own rules.
Your business data