Using the Companion
The companion keeps every client engagement on the AI Quick Up methodology. The page is the record; the agent in the chat bubble reads it, tells you what to do next, and records what the client said once you confirm it.
What it is
Each client engagement has one record: the channels in scope, a checklist of what we need from the client for each channel, the people involved, decisions, open items, and files. Two things work on that record:
- This page: where you see the state of every engagement and confirm or correct anything.
- The companion agent (the chat bubble, bottom right): it reads the record, plans your next steps, preps client sessions, and turns call notes into checklist entries.
The agent proposes; you decide. It can record what a client said, but only you can mark something Verified.
Signing in
- Go to aiquickup.com/companion, or click Sign in at the top right of aiquickup.com.
- Enter the e-mail address you were invited with and your password, then click Sign in.
- Admins then enter the 6-digit code from their authenticator app.
No password yet? Use E-mail me a sign-in link instead. Each link works once; use the newest e-mail. You are signed out after 60 minutes without activity.
The board
The first screen lists your engagements. Admins see all of them; consultants see the ones they are assigned to. Each card shows the client, package, stage, target go-live, the channels in scope with a readiness dot, and counts of open and blocking items.
| Readiness | Means |
|---|---|
| Grey: Not evaluated | The channel is out of scope, so the rules do not score it. |
| Red | Something is blocked. Nothing on this channel moves until it clears. |
| Yellow | Nothing blocked, but required items are not yet Verified. |
| Green | Every required item is Verified. Ready to connect. |
Click a card to open the engagement. Admins create engagements with New engagement.
Channels in scope
Every engagement starts with Knowledge base and Go-live, because every deployment needs both. Add the rest once the client has chosen them:
- Open the engagement and click Edit scope (admins only).
- Tick the channels the client confirmed: web widget, Shopify store, e-mail, phone, meeting bookings, Slack and Teams, SMS and WhatsApp, CRM, ticketing, quotes and proposals, or custom tools and MCP.
- Click Save scope. Each new channel gets its own checklist tab.
You can also ask the agent, as long as the client has actually decided:
Intake checklist
Below the engagement header is a tab for each channel in scope, with a count of required fields answered. Each row is one thing we need from the client. Click a field to record or change it.
| Field | What to enter |
|---|---|
| Value | What the client said, in their words. Use none when the answer is that there is none. |
| Status | Where it stands (below). |
| Source | Where it came from: Call 2026-10-07, E-mail from Dana. |
| Stated by | The client contact who gave it. |
| Notes | Your interpretation. Kept apart from the value so the record always shows what the client actually said. |
| Status | Use when |
|---|---|
| Not asked | Nobody has raised it with the client yet. |
| Asked | The question is out; you are waiting on the client. |
| Answered | The client gave a value, not yet checked. |
| Verified | You confirmed it, or a document proves it. Safe to build on. Only people can set this. |
| Not applicable | Out of scope for this client. Say why in Notes. |
| Blocked | Set by the rule engine when a check fails. You cannot set it by hand. |
Fields marked Required if… only matter when that condition applies, for example lead recipient only when the widget captures leads.
Rules and next actions
The rule engine checks the whole record every time anything is saved, on this page or by the agent. It sets each channel's readiness and stage, sets the engagement stage, and opens or closes open items tagged with the rule that raised them (W-F1, P-C1, and so on). Hover a rule ID to see its condition.
Next actions, at the top of the engagement, lists what to do first: escalations, then blocks, then fields still to collect, then warnings, then the next connect step on a Green channel.
| Open item | How it closes |
|---|---|
| Block | Closes by itself when the rule passes. To go ahead anyway, log a decision that starts Override W-F1: with the reason. G is notified. |
| Warn | Fix it, or click Accept if the client has decided to live with it. Accepted warnings stay closed. |
| Escalate | G decides, then clicks Decided. |
| Your own items | Click Done. |
An empty required field keeps a channel Yellow. A channel turns Red only when something is wrong: a feasibility check fails, an answer conflicts with another, or a field was closed out with no real answer or answered "unknown".
| Engagement stage | Means |
|---|---|
| Intake | Client people not yet named, or required fields not yet answered. |
| Planning | Everything answered; verifying and clearing blocks until channels are Green. |
| Build | Channels are Prepared, being connected and tested. |
| Go-live | Channels are live; first-week reviews and sign-off to come. |
| Signed off / Monitoring | Every channel reviewed and a sign-off decision logged; Monitoring if the client takes the monthly package. |
People and decisions
Name the client's prime contact, technical contact, and decision maker under Client people; the engagement cannot leave Intake without them. Add each channel admin with their channel, and tick Attends the connection session once confirmed.
Use Log decision for anything the client decided. The rules read these, so word them plainly:
Dee confirmed the channels in scope: web widget and e-mailunlocks the quote.Dee approved go-live for the web widgetlets a tested channel go live.Install through Google Tag Manager,Test on the live site after hours,Draft-first for 30 days,Duplicate cleanup before syncclear the matching warnings.Tuning items acceptedcloses the first-week review;Dee signed off the engagementcompletes it.
Connect steps
Each channel shows steps B1 to B5: B1 and B2 connect, B3 test, B4 go live, B5 first-week review. Click a step to mark it done with its evidence (a screenshot, test lead, transcript, or log link). A step without evidence does not count. Stages move as steps are done: Prepared (Green), Connected (B1, B2), Tested (B3), Live (B4, fallback plan recorded, go-live approved), Reviewed (B5).
Drafting deliverables
The Draft buttons under Next actions light up when the rules say a deliverable is ready:
| Deliverable | Ready when |
|---|---|
| Readiness assessment | Every required field in scope is at least Answered. |
| Deployment plan | Intake is complete, the client people are named, and no channel is Red. |
| Foundation quote | The decision maker is named and has confirmed the channels in scope. |
A draft opens in a new tab, built from the record. Click any text to edit it, then Save edits, Print or PDF, or Download for Word. Every draft is also saved to Recent files. Sections marked internal are for us; delete them before sending. Quotes are drafts for G's approval and are never sent by the agent.
Shopify stores
Add the Shopify store channel for any client selling on Shopify. On a Shopify store the chat widget and the store are one placement, so the quote counts them as one Foundation channel.
| In Foundation | Expansion, scoped and priced by G |
|---|---|
| The Quincer app installed on the store; product answers and recommendations from the catalog; in-chat add to cart | Order status, abandoned-cart recovery, discounts, subscriptions, inventory and stock alerts, returns and refunds, loyalty |
Record what the client wants under Commerce actions. Any Expansion feature there raises an escalation (SH-S1) for G to scope. Order status needs an agreed way for shoppers to prove who they are (SH-C1), cart recovery needs message consent (SH-F2), and a store with nobody who can install apps is blocked (SH-F1). Log when the old chat app comes off the store, so shoppers never see two bots (SH-X1).
Working with the agent
Open the chat bubble at the bottom right of the companion page. It only reaches the records when you are signed in on this page. Some things to ask:
Where are we?
It reads the record first, then gives the top three next actions, each with an owner, and for client items the exact question to ask.
After a client call
It matches what the client said to checklist fields and shows you a list of field, value, and source. Reply with what is right ("all correct", "record 1 to 4, skip 5") and it records those as Answered. Then mark them Verified on this page once you have confirmed them.
Before a client session
You get an agenda grouped by channel, who needs to attend, and what the client should bring.
What did the client say?
It searches the text of the engagement's uploaded files (notes, transcripts, e-mails, Word, PowerPoint, Excel, PDF, and text files), quotes the client's words, and names the file and date. It cannot search audio or images yet; paste a written transcript for those.
How do I...?
It answers from the Implementation Manual and this Help page and names the section it used. If the guide does not cover it, it says so.
Recording other things
What the agent will not do
- Mark anything Verified, or change an item someone already verified.
- Record a value you did not confirm, or invent a field, date, or client answer.
- Change channel scope unless you say the client has decided.
- Create blocking items; only the rule engine does that.
- Log an override of a Block rule; you do that on the page with Log decision.
- Contact the client, or quote AI Quick Up prices.
- Show a consultant engagements they are not assigned to.
Everything it writes is tagged Companion agent in the source and logged with your name.
Escalations
G is pulled in by an escalate item, raised by the rules (custom CRM objects, automatic customer-facing actions, a Block override, a Red channel within 10 business days of go-live) or by the agent when any of these come up:
- Scope beyond Foundation: extra personas, custom tools or MCP, CRM custom objects.
- Pricing changes, discounts, or anything off the menu.
- Recording consent, privacy, or regulated data (health, finance, minors).
- Any automatic write or customer-facing action.
- Client contacts contradicting each other, or a new decision maker.
- A channel still blocked within 10 business days of its target date.
Uploads
Use Upload on the engagement page for call notes, transcripts, voice memos, and client files (up to 50 MB). Files are stored privately with the engagement; only people assigned to it can open them. The agent can search and read the text of uploaded documents the first time you ask about them; audio and images are stored but not searchable, so paste a transcript for those.
Admin tasks
| Task | How |
|---|---|
| New engagement | New engagement on the board. Pick the consultant to assign. |
| Add a consultant | Team on the board. Enter the e-mail address they already use (any provider) and a name, then Send invite. They get the consultant role and an invite from g@aiquickup.com. |
| Assign or unassign a consultant | Open the engagement. The Consultants panel lists who is assigned; pick a name and click Assign, or click Unassign. |
| Remove someone's access | Team, then Remove access (click twice to confirm). They lose the page and the agent at once; everything they recorded stays. Restore access undoes it. |
Troubleshooting
| You see | Do this |
|---|---|
| "Too many sign-in e-mails were requested" | Sign in with your password, or wait a few minutes. |
| "That e-mail and password did not match" | Check the address is your AI Quick Up work e-mail. Ask G to reset the password. |
| The agent says it cannot reach the records | Make sure you are signed in on the companion page, reload, and start a new chat. |
| The agent talks about AI Quick Up pricing | You are in the public chat on aiquickup.com. Use the bubble on the companion page. |
| A channel you expected is missing | It is not in scope yet. Use Edit scope. |
| "No access" after signing in | Your account is deactivated. Contact G. |
Anything else: e-mail g@aiquickup.com.