AI Agents · Integrations
What an agent can touch, and what it cannot.
An agent is only as useful as the systems it can reach, and only as safe as the limits on that reach. For each connection: what data is accessible, which permissions it needs, what the agent may read or propose, and what always waits for a person.
Illustrative model A typical pattern. The exact reach of an agent is agreed per project and confirmed in a feasibility review.
Customer messages and the agent’s replies, through the WhatsApp Business Platform.
- Permissions required
- A verified business account, approved templates for business-initiated messages and recorded customer opt-in.
- What the agent can read
- The customer’s message and number.
- What it can propose
- Replies within the 24-hour window; template reminders.
- What needs approval
- Any template message that commits the business, and all reminders to many people at once.
- Workflow impact
- Faster first response and fewer missed messages. Meta’s fees and policies apply.
Contacts, deals, activity history.
- Permissions required
- A role limited to the accounts the user may see.
- What the agent can read
- Lead and deal records and recent activity.
- What it can propose
- Field updates, new leads, follow-up drafts.
- What needs approval
- Deal stage or value changes.
- Workflow impact
- More complete records, quicker follow-up.
Orders, purchasing, production and operational records.
- Permissions required
- Read-only service account scoped to the tenant.
- What the agent can read
- Order and job status, stock levels.
- What it can propose
- Task creation, exception flags.
- What needs approval
- Any change to an operational record.
- Workflow impact
- One place to ask across modules.
Invoices, payments and balances.
- Permissions required
- The Finance role. Others are refused without being told any figure.
- What the agent can read
- Invoices, balances, payment status.
- What it can propose
- Reminder drafts, summaries.
- What needs approval
- Every customer-facing reminder. Moving money is not permitted.
- Workflow impact
- Faster answers, fewer interruptions to finance.
Stock levels, usage and purchase orders.
- Permissions required
- Read-only for most roles.
- What the agent can read
- Stock and reorder levels.
- What it can propose
- Reorder suggestions and purchase-order drafts.
- What needs approval
- Placing any order.
- Workflow impact
- Fewer stock-outs and surprises.
Your own PostgreSQL or MySQL data.
- Permissions required
- A read-only database role limited to approved views or queries.
- What the agent can read
- Only what approved queries return.
- What it can propose
- Nothing directly: proposals go through the owning application.
- What needs approval
- Anything that would write data.
- Workflow impact
- Answers drawn from live data, not a stale export.
Messages the agent reads or drafts.
- Permissions required
- Mailbox access granted by an administrator, scoped to chosen folders.
- What the agent can read
- Incoming enquiries in the chosen folder.
- What it can propose
- Draft replies saved for a person.
- What needs approval
- Sending any email.
- Workflow impact
- Drafts ready for review rather than written from scratch.
Dashboards and reports built from operational data.
- Permissions required
- Read access to aggregated views.
- What the agent can read
- Counts and trends.
- What it can propose
- Report summaries and anomaly notes.
- What needs approval
- Publishing a report beyond the asker.
- Workflow impact
- Management questions answered without a report request.
Dispatch, scheduling, maintenance or other line-of-business tools.
- Permissions required
- Role-based access matching the user’s own.
- What the agent can read
- Queues, schedules, status.
- What it can propose
- Assignments and notifications as proposals.
- What needs approval
- Assigning work or notifying customers.
- Workflow impact
- Fewer calls to ask where things are.
- A customer’s message arrives through the WhatsApp Business Platform.Typical pattern
- The agent identifies the sender and runs an approved lookup for their order or case.Typical pattern
- If the question is about an invoice, it checks balances, and the sender’s role decides what may be shared.Typical pattern
- The conversation is logged against the customer’s record.Typical pattern
- A follow-up is prepared as a draft for staff.Typical pattern
- Question topics feed the dashboard, so patterns are visible to management.Typical pattern
Nothing here is automatic by default. Connections are built per project. Read access comes first; anything that writes or contacts someone is added later, behind an approval. See the architecture and the system integrations page.