Sign inTurn your help docs into an AI agent that answers customers in seconds, quotes the exact line it used, and hands refunds and edge cases to your team with the context attached.
No credit card. Live with one script tag.
Illustrative numbers from North Dock, our demo store. Not customer results.
01 / See it in action
A working walkthrough of the assistant for North Dock, a made-up store. Pick a question and watch it search the sources, quote the passage, verify the customer before it reads billing records, and send anything it can’t back up to you.
Answers from sources · billing records
Hi! I answer from North Dock’s published sources, look up orders and payments, and bring in a person when you need one. Pick a question below.
Scripted walkthrough on fictional data. No AI call, payment or message leaves this page. Create your one-hour live widget demo ↗
02 / How every answer is made
Every reply goes through the same four steps: ask, retrieve, quote, verify. If any step fails, nothing goes to the customer, and your team gets a review item with the full conversation.
VisitorHow many seats are in the student plan?
The student plan includes 25 seats.
Request · refund review · waiting for the owner
03 / Platform
From the first doc you import to the last ticket you close, you can see what the agent did and step in at any point.
How many seats are in the student plan?
The student plan includes 25 seats.
“…the North Dock student plan includes 25 seats.”
Student plan exception · grounding passed
Every reply comes with the exact passage it was built from, so customers and your team can see where it came from. A separate grounding check has to agree before anything is sent.
Incidents, requests and open questions land in one place, ranked by impact and urgency, with guarded status changes and private notes.
Add exceptions with start and end dates, or exact answers for the questions you never want reworded.
Paste text, upload Markdown or a PDF, or import a public URL. Nothing reaches a customer until you consent and publish.
Pick the colors, starter questions and placement, and choose which sites and pages show the widget. Optional lead capture asks for consent first.
Invoice ND-48213Paid · USD 49.00
Refund requestOwner review · nothing executes
Order and charge status, payment history, failed payments and retries, invoices, renewal dates and refund status from PayPal, Stripe, Dodo Payments, Razorpay, Paddle, Square, Adyen, Mollie, Chargebee and Lemon Squeezy, where the provider supports the lookup. Adyen covers order status and invoice links only, and Mollie has no invoice links. The customer verifies an order or invoice number and the email they paid with first, and only sees their own records. Read-only in test or live mode; refunds go to your review and nothing executes.
Take over a conversation and reply from Tickets. The visitor sees your message live in the widget and can answer back. A reply is emailed only if you choose to and the visitor left an address with consent. Messages are deleted with the conversation.
Set your time zone and opening hours. Visitors choose the AI or a person; outside your hours they see your away message and their request is saved for the team.
POST /mcp Streamable HTTP Bearer ap_ro_••••list_tickets readOnlyHintadd_text_knowledge_source stays unpublished
Point an MCP client at /mcp with a scoped, expiring AutomatePal token. Five read tools cover knowledge sources, unanswered questions, tickets, overview counts and billing status. Opt-in tools, each with its own scope, propose a text source that stays unpublished until you approve it, ask the bot a test question, reply in a conversation you already took over, or change working hours and the away message. No code execution, no takeover and no email.
04 / The owner’s view
Every conversation in one inbox, with the AI assistant, you and the visitor in one thread. Take over, reply inside the widget and hand back when you’re done. The overview keeps the counts and trends.
05 / Add-ons and integrations
Start with the built-in service desk, then add what you need. Each add-on is labelled available or in preview, so you know what works today.
Owner, admin, manager and agent seats with private invite links and an audit trail.
Scoped tokens that expire in 1 to 168 hours, for support, analytics and health metadata.
Event metadata signed with HMAC-SHA256 and delivered to a URL you own, with retries.
An optional contact step in the widget that asks for consent before saving an email.
Read-only order, payment, invoice, renewal and refund-status answers from 10 payment providers, where the provider supports the lookup, after the customer verifies. Adyen covers order status and invoice links only, and Mollie has no invoice links. Test or live mode; refunds stay review-only.
Connect an MCP client with a scoped, expiring token: read tickets, sources and counts, or propose a source that stays unpublished.
Refund, handoff and unanswered-question alerts. Rules save today; delivery starts after sender verification.
Unanswered questions grouped by theme, ready to turn into answers.
On the roadmapSlack · Zendesk · Freshdesk · Crisp · Google Chat · Messenger · WhatsApp Business · Zapier and Make. Not built yet.
06 / Trust
Built in from day one and covered by automated tests, not bolted on after launch.
Postgres row-level security separates every workspace. Tests deny cross-tenant reads, forged writes and foreign RPC calls.
Per-conversation and daily answer budgets are enforced before any model call, and refusals count.
Knowledge needs explicit processing and publishing consent. Owners can delete their workspace data themselves.
Payment provider credentials are encrypted with AES-256-GCM under a server keyring you can rotate. They are never sent back to the browser or written to logs.
Every provider request is checked against a fixed list of read endpoints, plus PayPal’s token sign-in, before it leaves the server. Anything else is refused, and tests confirm no request is sent.
The bot cannot charge, capture or refund. Refund requests become review items; you record approve or decline, and nothing executes.
Public preview on fictional data. Live payments stay off, and SOC 2, HIPAA and uptime SLAs are not yet claimed. Preview status ↗
07 / Questions
Setup steps, provider keys and the MCP tools are in the docs ↗. Have a question we didn’t cover? Send it to us ↗ and a person will read it.
A regular chatbot answers whether or not your content backs it up. AutomatePal attaches the exact passage it used, and a separate check has to agree before the reply is sent. When nothing in your sources supports an answer, the question goes to your review queue instead of becoming a guess.
Nothing is sent to the customer. The question becomes a review item with the conversation attached, and it shows up in your unanswered list so you only have to add the missing answer once.
Yes. Once you connect a payment provider, it answers order and charge status, payment history, failed payments and retries, invoices, renewal dates and refund status, where the provider supports the lookup. Adyen covers order status and invoice links only, and Mollie has no invoice links. Each answer shows the billing record it came from. Refunds always go to a person for a decision; the bot never moves money. Billing support is in preview.
PayPal, Stripe, Dodo Payments, Razorpay, Paddle, Square, Adyen, Mollie, Chargebee and Lemon Squeezy, each in test or live mode. Every adapter is tested against the provider’s published API contract on a local mock server. Razorpay and Lemon Squeezy are built from their API docs rather than a published spec, and Chargebee’s spec is labelled early access. Adyen covers order status and invoice links only, and Mollie has no invoice links. So far only PayPal has also been checked against a real sandbox account.
No. The bot never charges, captures or refunds, and no write call to a provider is allowed. A refund request opens a review ticket with the payment attached. You record approve or decline, and nothing executes.
The customer enters an order, invoice or payment ID and the email they paid with, and both must match the provider’s record. Verification lasts 30 minutes for that chat, every lookup stays inside that customer’s records, and the email is never stored.
Only if you choose to. After you take over a conversation, your replies appear live in the widget and the visitor can answer there. If the visitor left an email address with consent, you can also email your reply text to them; nothing else from the conversation is sent. Outside your working hours, visitors see your away message and can leave an email for a follow-up if you allow it.
One endpoint, /mcp, over Streamable HTTP, authorized with a scoped, expiring AutomatePal token. Read tools cover knowledge sources, unanswered questions, tickets, overview counts and billing connection status. They return metadata and counts, except the unanswered-questions digest, which includes the visitors’ question text. Write tools each need their own scope: one proposes a text source, which stays unpublished until you approve and publish it; one asks the bot a test question; one replies in the widget, only in a conversation you already took over in Tickets; and one changes the chat mode, working hours, away message, AI-or-person choice and contact field. There are no code-execution, takeover or email tools.
Yes. Invite admins, managers and agents with private links. Each role has its own permissions, enforced in the database, and every change is recorded with who made it.
No. Sources, testing and the widget’s look are all set up in the dashboard. Going live means pasting one script tag into your site, the same way you would add an analytics snippet.
Each workspace is isolated at the database level, API tokens are scoped and expire, and you can delete your workspace data yourself. AutomatePal does not yet hold SOC 2 or HIPAA certification.
Free preview. Fictional data. Real workflow.
Sign in → add a source → test it → paste one script tag.