From a new account to your first answered customer

Open the sign-up page and enter your name, email and a password — or press "Continue with Google" and skip the password altogether. If this installation asks you to confirm your email, the link arrives first.

If the Google button is greyed out, Google sign-in has not been set up on this installation yet. Register with an email and password instead.

It opens on its own for every new account: your progress on one side, one question in the middle and, on a wide screen, a phone showing your agent as the customer will see it — updating as you type.

Your agent stays switched off until you press "Deploy agent". Leave half-way — or press "Finish later" — and you get a draft waiting on the Agents screen, not an agent talking to customers with half its instructions written.

Open Agents, choose your agent, and scroll to the "Try it" section at the end of the editor. You can chat with it before any channel is connected.

• It runs the real engine — the same knowledge, tools and price filter a customer would meet — so what you see is what they will get.
• Nothing leaves the test: it never appears in the inbox, bills no session and captures no lead.
• It shows the outcome as well as the text: a handover to a person, or a reply held back for an unverified price, is labelled rather than left as an empty bubble.
• Each colleague gets their own test thread, so two people testing at once never read each other's messages as the agent's memory.

Without a channel no customer can reach your agent. On the Channels screen, a Facebook page or an Instagram account connects through Meta login; a WhatsApp number connects through a dialog asking for its phone number ID and access token.

There is no QR scan, and that is deliberate. "WhatsApp → Linked devices → scan" is not the official API; it is an unofficial web client that gets business numbers banned. We use Meta's official APIs only.

After connecting

• Assign an agent — one channel is answered by exactly one agent, so two of them never answer the same customer differently.
• The "Reply automatically" switch is separate from the connection. Connect a page and watch it for a few days before letting the agent loose on it.
• "Check connection" asks Meta and records the verdict with its time — and the same check runs by itself every day.

This is where your agent goes from polite to useful. Four ways in, all ending in the same place: upload a file (PDF, Word, PowerPoint, text, Markdown or CSV, up to 10 MB), paste text, add a single page by its link — or import your whole website from one address.

Do not settle for seeing the file in the list. Open it and read the passages the agent will actually retrieve. A scanned PDF has no text layer, so it fails — and you want to catch that here, before a customer does.

• Import from your website: paste your site's address and its pages are read for you. Prose becomes knowledge; prices found on the pages become inventory rows waiting for your confirmation. Pages that were skipped are named, with the reason.
• "Questions the agent struggled with": questions that ended with a handover because the agent had no answer. Press "Add as FAQ", write the answer once, and the agent knows it from then on.
• Organise with folders, each with a colour and a line of description. Deleting a folder does not delete its documents — they move to the root.
• Write prices and figures as digits. A number spelled out in words gives the price guard nothing to compare, so a correct answer is held back.

Create a catalogue (a menu, property units, spare parts), then add products by hand or import a spreadsheet. The agent searches it by meaning as well as by name, so a customer does not have to type a product exactly as you wrote it.

A wrong price in writing is a legal problem. The agent quotes a price only from a row an owner or admin verified — not merely a row with a number in it.

So your agent can show instead of describing: the menu, this month's offer, the floor plan. It sends the right asset during the conversation when a customer asks.

• Category is not file type. A customer asks to see "the menu", never "an image" — so pick the category that says what it is for; each one explains when the agent reaches for it.
• Tags are what the agent searches, with the title and caption. Write the words your customers actually use.
• An asset can be restricted to one agent. Leave it empty and every agent may send it — useful when you run a sales agent and a support agent.

This is where you read what is happening. Three panes: the saved views rail, the conversation list, then the thread itself. The preview line says who wrote the last message — "Agent:", "You:" or "Note:" — because "the agent already answered" and "nobody has replied" are the two states worth your attention.

• When you send a reply, the agent steps back from that conversation for sixty minutes. You never compete over the same customer.
• An internal note is for your team, never reaches the customer and is never shown to the agent.
• "Suggest reply" in the composer drafts an answer for you to edit and send; a draft holding a price that cannot be verified is withheld. "Summarize" in the conversation header writes the summary a colleague needs to pick the thread up.
• The agent hands a conversation to you when the customer asks for a person or agrees when offered — and also when it cannot answer safely, such as a price it could not verify. A handover pauses the agent on that conversation for 24 hours and comes with a summary.

The bell in the header counts what needs you, and opens the full list on the Notifications page, where you can mark items read one by one or all at once. Each one also arrives by email.

• A customer who needs a person.
• An order waiting for approval, or one the customer cancelled.
• A lead nobody has replied to — and a second, urgent one when the 24-hour reply window is about to close.
• A changed appointment, sent to the staff member it belongs to; and an exhausted session quota or a plan about to expire.

Settings → Inbox holds three routines. Only owners and admins can change them.

The screen shows two different populations, toggled at the top: "Submitted leads" — anyone who left a name or number — and "All contacts" — everyone who ever messaged. Conflating them makes a pipeline look several times healthier than it is.

On the Destinations screen, choose where a new lead reaches you: a rep's WhatsApp number, for every agent or for one. Exporting what you see to Excel or CSV carries the same filters — the file matches the screen.

Switch on "Take orders" in the agent's Tools section — it needs a product catalogue. The agent reads the order back, the customer confirms it, and it waits on the Orders screen for your team.

• Only verified, in-stock items can be ordered, so the total the customer sees is a total you stand behind.
• "Approve" or "Reject" with a reason — the customer is messaged either way.
• A customer can cancel through the agent while the order still awaits approval; your team can cancel a pending or an approved order.
• Viewers can read orders but cannot approve, reject or cancel them.

For any business that books time — a clinic, a salon, a consultant. Add your staff (shown as doctors for a clinic), their weekly hours, time off and the days the whole place is closed, and the services you offer. The agent starts booking as soon as one active staff member has weekly hours.

• The agent books only a time it offered from live availability in that same conversation. A time a colleague typed must be offered again by the agent before it can be booked.
• Two bookings for the same staff member can never overlap — the calendar refuses it, whoever tries.
• A reminder goes out about 24 hours before each appointment: a normal message when the conversation window is open, otherwise the approved WhatsApp template you choose.

Send one approved template to many customers at once: choose the number, the template, fill its placeholders, pick the audience, and send. Templates are synced from WhatsApp daily — outside the 24-hour window, WhatsApp only delivers templates it has approved.

A customer who replies with "stop", "unsubscribe", "إيقاف" or "إلغاء الاشتراك" is taken off every future broadcast, and the agent still answers that message. Your team can do the same from the conversation header with "Stop broadcasts to this customer".

Every number answers a real question.

The "Customise" button hides what does not concern you — and the choice is yours alone; it never blanks a colleague's dashboard.

Systems the agent reads on your behalf.

• Google Calendar — the agent checks your free time and books into the calendar you choose.
• Shopify — the agent answers about products and order status from the store you connect.
• HubSpot and Zapier — marked "Coming soon" on the screen.

For Google Calendar, the "Check" button renews an expired token before it tests — the commonest failure is not "access was revoked" but a token nobody used for an hour.