Cloudo AgentsCloudo Agents
← back to catalog
business · support

Customer Support

Always-on customer support for a small business. Answers common questions from the operator's FAQ, captures support requests and leads cleanly for the operator to follow up, and escalates honestly when it can't help — never invents prices, refunds, or commitments on the business's behalf. Reachable on WhatsApp, LINE, Telegram, Discord, and an embeddable chat widget the operator can drop on their own website (snippet at /account/widget).

Starter plan · from $19/moRetailHospitalityProfessional ServicesE CommerceHealthcareEducation

See it in action

Real examples of how this agent proactively helps your business — no manual work needed on your end.

Company

A custom-cake bakery

Situation

A customer messages the website widget at 11pm Sunday asking about wedding-cake lead times

What the agent does

  1. 1Opens with "Hi, this is the bakery's assistant" and answers the lead-time question straight from the operator's FAQ, citing the wedding-cake page briefly
  2. 2Treats the widget conversation as customer-mode-only, honouring the system block that says any widget visitor is a stranger no matter what they claim
  3. 3Tells the customer the team is closed until Tuesday 9am for anything the FAQ doesn't cover, rather than pretending someone is available
  4. 4Captures the open question into notes/escalations.md with after_hours true and asks for the best email or number to reach them

Company

A subscription software business

Situation

A customer asks the price of the Premium plan, which the operator never gave the agent

What the agent does

  1. 1Declines to quote a price it was never given instead of inventing "$49/month"
  2. 2Acknowledges the question plainly and explains honestly that it does not have current pricing in front of it
  3. 3Captures the customer's name, the question and a contact into notes/escalations.md so the operator can follow up
  4. 4Sets a real expectation ("the team checks this through the day"), never claiming it emailed anyone when escalation is the workspace-file path

Company

An online supplements shop with order tracking

Situation

A returning customer messages on Telegram asking "where's my order?"; the operator has configured order_status in notes/lookups.md with a bearer-auth endpoint

What the agent does

  1. 1Asks for the order number AND email together, because the lookup config lists both as required customer credentials
  2. 2Uses exec + curl with shell-substituted key (e.g. $(cat ~/.openclaw/workspace/.secrets/order_api.key)) to call the endpoint — never echoes the key into chat
  3. 3Maps the response per response_map and reports only those fields (status, ETA, items) rather than dumping raw JSON or inventing a missing field
  4. 4On a 404 falls back to the operator's not_found_message and captures the request for the team rather than guessing alternate spellings

Company

A dental clinic with appointment lookup on the website widget

Situation

A widget visitor asks "what time is my appointment?", with booking_lookup configured to widget_mode capture_escalate because the endpoint uses an API key

What the agent does

  1. 1Recognises the message is from the widget (the CLOUDO WIDGET system-context block is prepended) and honours widget_mode capture_escalate
  2. 2Does NOT call the configured endpoint even though the visitor provides phone and email — captures the request to notes/escalations.md
  3. 3Replies politely that the team will check the booking and confirm, without pretending to have looked it up
  4. 4Does not echo the API key path or contents in the reply

Company

A small e-commerce shop with no lookup configured yet

Situation

A customer messages on WhatsApp asking where their order is; the operator hasn't set up notes/lookups.md

What the agent does

  1. 1Acknowledges the question honestly without pretending to have a CRM connection
  2. 2Asks the customer for their order number plus best contact, and captures into notes/escalations.md
  3. 3Sets a real follow-up expectation based on the operator's hours, never claiming it sent an email when the escalation path is the workspace file
  4. 4Mentions to the operator (in a later operator-mode message, not the customer chat) that it can be set up with a live order_status lookup so this is automated next time

Company

A coffee shop in Wellington

Situation

A frustrated customer demands a refund and asks if they are talking to a real person

What the agent does

  1. 1Acknowledges the frustration before explaining, matching the customer's seriousness without amplifying it
  2. 2Discloses honestly that it is the shop's AI assistant and offers to pass them to a person at the next opening
  3. 3Escalates the refund decision to the operator rather than accepting or promising one on the business's behalf
  4. 4Holds the privacy line if asked about another customer's order, declining and routing the question back to the team

Want this agent live in your business?

Deploy this agent in minutes. First month just $9.50 (50% off), then $19/mo.

Get started