Features

Everything Tendo does

Everything below is built and works today.

Knowledge

What Tendo answers from. It uses only what's here and says so when the answer isn't.

Your help center or website. Tendo reads up to 200 pages on the same site under the address you give, follows robots.txt, and reads it again whenever you press the button.
Files. PDF, Word, text, Markdown, HTML and CSV, up to 10 MB each: policies, product guides, an exported FAQ.
Pasted text. A policy or the answers you send often.
Past replies. Paste or upload replies your team has sent. Tendo uses them for facts and to match how your team writes.
Answers it learns, with your approval. When a teammate answers something Tendo couldn't, it's suggested as a new answer. Edit it, approve it or reject it; nothing is used until approved.

Only from your docs, with citations. Every reply names the help docs it relied on: the team sees them on the draft, and customers get links to the public pages.
Says when it doesn't know. No matching doc means no AI reply: the conversation goes to your team instead of a guess.
In your words. Write how replies should sound ("warm and brief, say we, not I") and add past replies as examples.
Draft for approval or send automatically, per inbox. Start with drafts while you get to know it, then let confident, cited replies go out on their own in the inboxes you choose.
Try it first. Ask what a customer would and see exactly what Tendo would do, with the passages it found, before any customer writes.

Email. Each inbox has a forwarding address. Forward your support address (Gmail, Google Workspace, Microsoft 365 or any provider) and customers keep writing to you as before. Replies go out in your business's name and come back into the same conversation.
Website chat. One line of code adds a chat button to your site (Shopify, WordPress or any page). Tendo answers there with the same rules, and asks for an email address when it hands over so your team can reply later.
Safe by default. Bounces, out-of-office replies and mailing lists never get an answer, and you can limit the chat to your own websites.

Your rules decide when a person takes over. A confidence threshold you set, topics that always go to a person (refunds, legal, cancellations, or your own), a request for a person, or an upset customer.
Clean handovers. Your team gets the customer, the question, the reason and a short summary, with Tendo's draft when it wrote one. Teammates who want it get an email.
A shared inbox. Assign conversations, leave internal notes, mark them needing a reply, waiting or resolved, and filter by inbox, assignee or drafts to approve.
Tendo stays out once a person steps in. A teammate's reply pauses Tendo in that conversation until someone turns it back on.

The numbers that matter. Conversation volume by day and channel, AI-resolved rate, handover rate and why, first response time (median and 90th percentile, Tendo alone and with your team), and how many drafts were approved, edited or discarded.

Export and delete. Download everything as JSON or every conversation as a spreadsheet, forget one customer, or delete the workspace. Conversations are deleted automatically after the period you choose.
Roles. Owner, admin, agent and viewer. Only the owner handles billing.