Every question answered.Every miss handled.

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.

No. After you take over a conversation, your replies appear live in the widget only and the visitor can answer there. Nothing is emailed. 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.

It works through multi-part questions one piece at a time, follows date-limited exceptions you set, answers in the customer’s language when your sources cover the topic, and ignores instructions written into a message.

It replies in the language the customer writes in when your sources cover the answer. We have tested English, Hindi and Telugu so far.

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.

About an hour: add a source, test a few questions, set the widget’s look and starters, then paste one script tag on your site.

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.