An AI intake agent for new client enquiries
When a new enquiry arrives by form, email, or chat, the agent reads it, records the lead in your CRM, drafts a reply, and creates the follow-up. A person on your team approves the reply before it goes out.
The audit checks the real workflow and tool access before we recommend a build. These are the conditions that usually make the first scope practical.
- New enquiries land in a shared inbox or form and wait for someone to read them
- Lead details are retyped into the CRM by hand
- Urgent requests sit in the same queue as general questions
- First replies are similar enough to draft, but someone must still check them
One path from the original input to a recorded outcome, with the exception route designed at the same time.
- 01
Receive the enquiry
Watch the agreed form, inbox, or chat channel and keep the original message with the lead.
- 02
Extract and classify
Pull out the contact details, the request, and any dates, then rate urgency by the rules you set.
- 03
Update the CRM
Create or update the lead record, set the stage and owner, and add the follow-up task.
- 04
Draft for approval
Prepare a reply in your tone and hold it for a person to approve, edit, or discard before it is sent.
Included in the handoff
- Intake rules for one channel: fields to capture, urgency categories, and routing
- A CRM integration that creates and updates lead records and follow-up tasks
- Reply drafting with an approval step for the person who owns the lead
- A run record per enquiry and an operating guide for the intake owner
How your team stays in control
- No reply leaves without a person approving it.
- The agent writes only to the CRM fields agreed in scope.
- Enquiries it cannot classify go to a person with the original message attached.
- Each run shows what was read, what was written, and who approved the reply.
The first call is used to verify the workflow, source material, integrations, approval points, and practical first scope.
Which channels can the agent watch?
The first scope covers one channel, such as a website form, a shared inbox, or a chat tool, provided it offers a practical integration path. More channels can be added once the first one is running.
Can it send replies on its own?
No. In the first scope every reply is a draft that a person approves. If you later want routine replies sent automatically, that is agreed separately with its own rules and fallback.
How does it decide what is urgent?
You define the urgency rules during discovery: keywords, request types, deadlines, or customer attributes. The agent applies those rules and sends unclear cases to a person.
Which CRMs does it work with?
Any CRM with a usable API or integration, which we confirm during the audit. The strip on the homepage shows examples of tools we integrate with.