A database your team can see.
A shared sheet is transparent: everyone can see what the agent added or changed, and corrections are just edits. That makes it a good place to start.
Sheets have limits on size and concurrent writes. When a build outgrows them, we move the data to a database and keep a sheet view if your team likes it.
What agents do in Google Sheets.
Enquiries logged with source, score and next step.
Each proposed message or action as a row; tick to approve.
Numbers collected in a sheet and summarised automatically.
Agents answer customers from a sheet you maintain.
Duplicates, formats and missing fields fixed with a log.
How access works.
A service account only sees what you share with it.
What it costs.
All prices excl. VAT. "From" covers a standard scope; your fixed quote comes from the Blueprint. Model and messaging fees (for example WhatsApp per-message charges from Meta) depend on volume and are estimated in the Blueprint.
Common questions.
Is a spreadsheet safe enough?
For low-risk data and early stages, yes, with access limited per sheet. Sensitive or high-volume data belongs in a proper database.
Does it work with Excel?
Yes, through Microsoft Graph for files in OneDrive or SharePoint.
Can we move to a CRM later?
Yes. The agent logic stays the same; we switch where it reads and writes.
Want this in your business?
Tell us how you work today. We'll tell you honestly what AI can take off your team's plate, what it costs, and whether we are the right fit.