One support category
A defined request type, approved guidance, and escalation rules for one support team.
Customer support AI
AI for customer support. Replies ready to review.
We bring approved guidance and an editable reply draft into your support workflow. Start with one recurring ticket category; your agents review what gets sent.
From $4,500 USDOne-time project. Software and usage billed separately.
30 minutes with the co-founders. Check fit, tools and the next scoping step.
Is this the right
first project?
Before an agent can help, they often have to reconstruct the case. The request is in the help desk, the order details are elsewhere, and the applicable policy takes another search. Good support preparation assembles that context and makes unanswered questions obvious, so the agent can focus on resolving the issue.
A good fit when…
Support agents repeatedly search for the same policy before answering common questions.
Requests bounce between queues because categories or ownership are unclear.
Reply drafts need to reflect current guidance and flag missing customer context.
Your first project, priced.
AI support agent assist
From $4,500 USD
One-time project. Final scope and price agreed in writing.
Put relevant guidance and an editable reply draft beside one recurring type of support ticket, ready for your agent to review.
Book a free scoping call ↗30 minutes with the co-founders to check fit, tools and the next scoping step. No obligation to proceed.
Included in the starter scope
- One ticket category, one support team, and one agreed help-desk or review interface.
- An approved support knowledge set with a named source owner.
- Suggested triage, source-linked policy context, and editable reply drafts.
- Tests for missing customer details, conflicting guidance, and specialist escalation.
- A working review flow and instructions for maintaining the guidance and checking drafts.
- Quoted separately
- Autonomous customer replies, phone handling, additional channels, and actions such as refunds or account changes need separate scope.
- A larger project
- Quoted after scoping — Add ticket categories, permitted account context, more channels, or a separately scoped customer-facing assistant. This is an alternative scope, not an add-on to the starter price.
- Optional ongoing support
- Optional monitoring and maintenance are quoted for agreed categories, sources, and coverage; platform and model usage are separate.
- Timing
- We set the delivery plan after checking the help-desk interface, approved policies, and representative tickets.
All prices are in USD. Third-party software, API usage, hosting and any telephony charges are separate. Support is optional; its coverage and limits are agreed separately. New workflows need a new scope.
Tangible work
What you take away.
Editable drafts with context
Suggested triage and source-linked guidance beside a reply draft in one agreed help-desk or review interface.
A support quality routine
Representative tickets and tests for missing context, conflicting guidance, and specialist cases, with instructions for maintaining sources and checking drafts.
Let’s check the fit.
Bring one task and your current tools. We’ll discuss the first step in a free 30-minute call.
See the workflow.
Then consider what comes next.
- 01 / The starting point
A customer asks to change an order without including the details needed to identify it.
- 02 / The right context
Classify the request and find the current order-change policy from the approved support material.
- 03 / Prepared for review
Prepare a reply asking for the missing reference, with the relevant policy beside the draft.
- 04 / A person decides
The support agent checks the context and chooses the response or escalation that fits the case.
Related workflows to explore
Additional workflows are scoped separately.01
Prepare the first support response
Sort requests, assemble useful context, and put a draft beside the evidence an agent needs.
Explore the workflow 02Find current internal guidance
Make approved support knowledge easier to use, with source references and visible gaps.
Explore the workflow 03Hand a return to operations
Connect the support conversation to the separate review of the physical item and its disposition.
Explore the workflowFrom first conversation to handoffA clear start.
A clear start.
An agreed finish.
- 01
Follow the agent's first steps
Trace a request from arrival to resolution. Identify the useful categories, recurring questions, missing context, and sources the team actually trusts.
- 02
Bring context into the queue
Connect the agreed source material and build the preparation flow. Keep the ticket, supporting policy, draft, and open questions together in the review experience.
- 03
Check real support situations
Test incomplete requests, several issues in one message, a policy change, and a case that needs specialist handling. Agree how the team corrects drafts and reports gaps after rollout.
Agree the scopeAgree the scope
Agree the scope
and the limits.
The starter assists a person reviewing one ticket category. Automatic customer replies, phone handling, additional channels, account lookups, refunds, and account changes require a separate scope and agreed authority.
Security and data questions ↗A few useful answers
Before we begin.
How much does a first project cost?
AI support agent assist starts at $4,500 USD for the starter scope shown on this page. We confirm access, scope, exclusions, timing and a written price before work begins. Third-party software and usage charges are separate; ongoing support is optional.
What happens on the free scoping call?
In 30 minutes, we discuss one task, your current tools and the result you need. We check whether the starter fits and what is needed for a written proposal. If paid discovery is needed, we explain its scope and price first. You do not need a prepared brief or a paid assessment to book the call.
How will we judge whether the project is useful?
We agree a baseline and acceptance checks with the person who owns the work. Sample tickets produce editable drafts with relevant guidance; missing context and escalation cases stay visible. Where relevant, we also compare manual effort, correction work and operating costs. These checks guide the handoff; they are not a promise of revenue or savings.
What does a first customer support AI scope include?
Choose one ticket category and the support agents who will review its output. The scope can include routing suggestions, permitted account context, source-linked guidance, and reply drafts. Test incomplete requests, mixed topics, and policy exceptions before extending the audience or automating replies.
Does this require a customer-facing chatbot?
No. A first implementation can prepare work inside the support team's queue. A customer-facing interface has additional knowledge, escalation, and channel requirements. Agree that choice with the support owner, including which actions and messages need approval.
What determines customer support AI cost?
Cost depends on channels, help-desk access, request categories, knowledge preparation, and the depth of account context. Evaluation and escalation design are part of the work. Ongoing costs can include model usage, platform subscriptions, and maintenance of policies and test cases.
What affects the implementation schedule?
Timing depends on approved support guidance, help-desk integration options, representative tickets, and reviewer availability. Gaps in policy ownership or conflicting sources need to be resolved. Agree the first category, audience, and acceptance checks before setting the rollout plan.
Can it work with our existing help desk?
Assess the help desk's interfaces, permissions, field conventions, and draft-review experience first. These determine whether prepared work belongs in the current queue or a companion view. Access to customer information and any write or send actions must be explicitly scoped.
How does support AI stay current when policies change?
Give approved guidance a named owner and a refresh routine. Add changed policies and previously failed tickets to the evaluation set. Decide who reviews incorrect routing or unsupported drafts, and whether continuing operational support is handled internally or included in a separate agreement.