Customer support flow mock-up

    Show how a support conversation should go, for a deck or for training. It is a scripted example with invented people, never a real customer story.

    Try it: start from this sample

    Customer
    Friday, Mar 14
    Customer2:05 PM
    My invoice shows two charges for this month.
    Agent Ana2:06 PM
    Sorry about that. I can see both charges and I am looking into it now.
    One is a duplicate. I have refunded it, and you will see it in 3 to 5 working days.
    Customer2:08 PM
    Thanks, that was quick.
    Message Customer
    Open this sample in the editorThis look needs a paid plan.

    What the mock-up is for

    A support flow mock-up teaches or sells a process: acknowledge, check, fix, confirm. It belongs in a training slide or a sales deck that explains your approach. It does not belong anywhere as a story about a real customer. Everything in the sample is invented, from the name to the invoice. The Slack-style look needs the Standard plan; the Free looks such as WhatsApp or Discord work if you want to stay on Free.

    Show a good reply structure

    Walk the reader through four moves. First, acknowledge the problem in the customer's own words. Second, say what you are doing, not just that you are sorry. Third, give the outcome with a time. Fourth, check that the customer has what they need. Mark each move with a caption beside the image rather than inside the bubbles, so the chat looks natural.

    Show a hard case too: a customer who is angry, or one who asks for something you cannot do. Training improves when people see the difficult reply.

    Keep the agent messages short enough to read in one glance. Long replies in a training deck hide the structure you want people to see, so split a long answer into two bubbles, each doing one move.

    Do not present it as real

    Never label it a customer quote, a review or a testimonial, and never attach it to a named client. If you want to show real feedback, get written permission and use the real words. Add a caption such as Illustrative mock-up, scripted example, and keep personal data out of every bubble.

    Tips

    • Put the refund or fix and the timeframe in the same message.
    • Use plain words, with no scripts that sound like a robot.
    • Show one conversation per slide with its lesson written beneath.
    • Invent every detail, including order numbers and amounts.
    • Add a short label to each image before it leaves the team.

    Questions

    Can I use a real customer conversation?

    Only with the customer's permission and their actual words, and without personal data. A mock-up built in ChatsRat is a scripted example and should never be presented as a real exchange.

    Which look should I choose?

    Slack-style suits internal and workplace tone, and Messenger or WhatsApp suit consumer support. Slack is on the Standard plan; the table of looks in the editor shows each plan.

    Can I show several agents?

    Paid plans allow up to four people in a chat. The Free plan allows two. A group view can show a handover from one agent to another.

    Is it a testimonial?

    No. A testimonial is a real person's words. This is a mock-up with invented people. Presenting it as a testimonial would mislead people and is not allowed.

    Use it for simulated, labelled content. ChatsRat makes mock-ups and fictional conversations for creators, designers and teachers. Do not use it to pass off a made-up conversation as a real one, to impersonate a real person, or as proof of anything. See the Acceptable Use policy.

    About the watermark. Exports on the Free plan carry a visible ChatsRat watermark, and every export carries an invisible mark that the verify page can read. Plans list what changes on paid plans.

    ChatsRat is not affiliated with, endorsed by or sponsored by any messaging app. App names on this page describe a style only.

    All tools