Skip to main content
3rd place, AWS CDS Agentic AI Partner Hackathon

The AI care agent that follows every order through

For online brands: CareBridge writes first when a payment fails, a delivery fails, an order arrives, a return is requested or a complaint comes in. Then it works the case on RCS, WhatsApp, SMS, email, website chat and phone until it is settled.

CareBridge · Cases
  1. Eventdelivery_failed

    Washer delivery missed. Case opened.

  2. RCSsent

    Your washer delivery missed you today. Pick a new day?

    Give feedbackI need helpCall me

  3. Timer24h

    No reply. Follow-up due.

  4. RCSfollow-up

    Still want the washer this week? Reply or tap Call me.

  5. Phonevoice consent

    Outbound call. Same case, same history.

  6. Toolconfirmed

    Delivery rescheduled for Thursday.

  7. Caseclosed

    Settled on the channel the customer answered.

After checkout

Post-purchase support is still chased by hand

  1. 01

    Failed payments and deliveries are chased by hand

    Someone on the team spots the failed card or the missed delivery, writes to the customer, waits, and writes again. Most of the day goes on follow-up.

  2. 02

    Customers tell the same story on every channel

    The text thread, the email and the phone call each start from zero. The customer explains the order three times and the agent on the phone sees none of it.

  3. 03

    Chatbots promise refunds nobody approved

    A chatbot told what to say in a prompt can be talked into a refund, a discount or a date the business never agreed. Then support cleans up after it.

See how CareBridge takes the follow-up off your team
Packed orders in cardboard boxes on warehouse shelves, waiting to ship

Five order events, six channels, one case

  • Payment failed
  • Delivery failed
  • Delivered
  • Return requested
  • Complaint
  • RCS
  • WhatsApp
  • SMS
  • Email
  • Website chat
  • Phone

How it works

Four steps from store event to settled case

CareBridge is not a chat widget waiting for questions. It starts on the order event and keeps going until the case is closed or a person has it.

  1. Step 1

    A store event arrives

    Your store posts a signed webhook when a payment fails, a delivery fails, a return is requested or a review is negative. Delivery events come through Amazon EventBridge.

  2. Step 2

    The agent opens a case and writes first

    One case per order event. The agent picks a channel the customer consented to and sends the first message itself. No one has to ask.

  3. Step 3

    It follows up, switches channel, calls

    No reply in 24 hours brings a follow-up. A bounce switches the channel. A large order, or two unanswered messages, can bring one phone call.

  4. Step 4

    It settles the case or hands it to a person

    The case closes when the order is sorted. Anything the agent may not decide goes to your team with a summary and a link to the case.

See what it does at each stage of the order

The order lifecycle

Five playbooks, each with its own tools

Each playbook has its own prompt and gives the agent only the tools that playbook allows. Pick a stage.

payment_failed

Payment failed

Tells the customer the payment did not go through and sends a link to pay again.

No offers in this playbook.

Tools in this playbook

  • Send a payment link(allowed)
  • Reschedule delivery(not available in this playbook)
  • Update the address(not available in this playbook)
  • Make an offer(not available in this playbook)
  • Guided help and links(not available in this playbook)
  • Send a spare part(not available in this playbook)
  • Request a technician(not available in this playbook)
  • Request a refund(not available in this playbook)
  • Start a return(not available in this playbook)
  • Record feedback(not available in this playbook)

Channels

One case record across six channels

Text, chat, email and phone all work the same case, so a call picks up where a text thread stopped. The agent picks only channels you switched on and the customer consented to.

  • RCS

    Messages with buttons: Give feedback, I need help, Call me. Phones without RCS get SMS with links.

  • WhatsApp

    Opens with an approved template and moves to free conversation once the customer replies, inside the 24-hour window.

  • SMS and email

    Plain SMS, and branded HTML email sent through Amazon SES.

  • Website chat

    On Amazon Connect. The agent says it is automated, checks the order number and delivery ZIP code, then works the case in the chat.

  • Support inbox

    Email to your support address through Amazon Connect. Replies land on the same case.

  • Phone

    Inbound and outbound calls on Amazon Connect, spoken by Amazon Nova 2 Sonic. Known numbers pick up their open case.

Nobody tells the story twice

  • A text during a call

    It is acknowledged, shown to the voice agent, and answered once the call ends.

  • History on every call back

    The agent sees the order’s earlier cases, how each ended and the parts already sent.

  • Preferences kept between orders

    Contact preferences are stored in Amazon Bedrock AgentCore Memory.

  • Seven-day reopen

    A closed case reopens if the customer writes again within seven days. Anything said on a chat or call can be sent in writing by email.

See the limits the agent cannot cross
A customer holding a phone and a coffee, reading a message

On a call

SMS · during callCan you also email me the manual?

Acknowledged on the call. Answered by email after it ends.

Guardrails

The limits live in code.

Consent, opt-out, offer caps, the refund ceiling and contact limits are enforced by the platform, whatever the AI is told or asked. The text agent and the voice agent both go through them.

CareBridge guardrails: each rule, its value, and who can override it
RuleValueWho can override
Largest discount15% of the order total, counting everything given on the caseA person, in the console
Largest store credit20% of the order total, counting everything given on the caseA person, in the console
RefundsThe AI can only request one. Ceiling 100 in the order’s currency, set in codeA signed-in support lead approves or declines
Consent and opt-outConsent per channel. STOP, UNSUBSCRIBE, CANCEL, END, QUIT or a spam complaint opts out before the agent runs againNobody: the customer opts back in
Identity checkOrder number and delivery ZIP code before anything beyond how-to help. Wrong codes share one daily limit across calls, chats and messages. The address is never read outNobody
Voice call tokenOne call, one case, expires after two hoursNobody
Action linksCall me, photo upload, feedback, chat and help links work once, for 24 hours, on one caseNobody
Never twiceEach send is recorded before delivery. Each turn runs under a one-time claimNobody
No claim without proofThe agent may not say something was sent, shipped or booked until the tool result shows itNobody
See how you go live, one channel at a time

Operator console

Your support team stays in charge

Every case in three views: the conversation across every channel, each call’s transcript, and every step the AI took with each tool call’s input and result.

CareBridge console · signed in with Cognito as Support lead
  • RCSYour washer arrived today. How is it going?
  • RCSIt shows E21 and won’t drain.
  • RCSLet’s check the drain filter first. Step 1: unplug the washer.
  • PhoneStill not draining. I’d like a refund.
  • PhoneI’ve asked our support lead to review a refund. You’ll hear back on this case.

Anyone who asks for a person, on any channel, lands in that channel’s queue with a summary and a link to the case. Contact Lens flags negative sentiment on calls.

  • Web chat
  • WhatsApp
  • RCS and SMS
  • Email
  • Phone
See the eight adoption steps

Adoption path

Eight steps from first call to live channels

You can test every case before a single message goes out. FactualMinds works beside your team at each step.

A laptop on a tidy desk by a window, ready for a working session
  1. Step a: Discovery call and demo

    We walk your order flow and run CareBridge on test orders.

    FactualMinds: Runs the demo and maps your five order events.

  2. Step b: Deploy into your AWS account

    AWS CDK deploys the stack. The dev environment comes first.

    FactualMinds: Onboarding: the first deploy, side by side with your engineers.

  3. Step c: Connect your store

    A signed webhook for order events, and Amazon EventBridge for delivery events.

    FactualMinds: Helps map your store’s events to the five playbooks.

  4. Step d: Turn on channels as they are approved

    Email, SMS, RCS, WhatsApp and Amazon Connect, each one a switch.

    FactualMinds: Channel registration help and the Amazon Connect setup.

  5. Step e: Dry run

    Every case worked end to end with nothing sent. You read what it would have said in the console.

    FactualMinds: Reviews the dry-run cases with your support lead.

  6. Step f: Go live, one channel at a time

    Staging first, then prod.

    FactualMinds: Watches the first live cases with you.

  7. Step g: Operate

    The Needs a person queue, refund approvals, transcripts, CloudWatch alarms and the budget alert.

    FactualMinds: Answers questions while your team settles in.

  8. Step h: Improve

    Read the audit trails and evaluations, then tune playbook prompts and follow-up timing.

    FactualMinds: Reviews trails and evaluations with you and proposes changes.

Book a demo

We run it on your own test orders, with nothing sent.

Built on AWS

Runs on AWS, inside your own account

The agent is built with Strands Agents on Amazon Bedrock AgentCore Runtime. Text runs on Amazon Nova 2 Lite on Amazon Bedrock by default, and you can change the model. Voice tools reach Amazon Connect as MCP tools through AgentCore Gateway. Messages go out through AWS End User Messaging and Amazon SES.

  • Amazon Bedrock
  • Amazon Bedrock AgentCore
  • Amazon Nova 2 Lite
  • Amazon Nova 2 Sonic
  • Amazon Connect
  • AWS End User Messaging
  • Amazon SES
  • Amazon DynamoDB
  • Amazon EventBridge
  • AWS CDK

484 automated tests run without AWS or a real model. Scenario evaluations test the real model against its rules, and scripted support-line calls run against the live agent.

For your CTO

  • Runs in your account

    Deployed with AWS CDK into your AWS account. Case data stays in your DynamoDB table.

  • Least privilege per channel

    Channels are config switches. A channel that is off gets no permissions at all.

  • Signed webhooks

    POST /events with an HMAC-SHA256 signature. Returns 202 when the event is queued.

  • Private photo bucket

    Customer photos sit in a private bucket and are deleted after 30 days.

  • Every AI action audited

    Each tool call is stored with its input and result. CloudWatch alarms are built in.

POST /events
X-Signature: sha256=9f2c41d7…
{ "type": "payment_failed", "order": "48213" }

← 202 Accepted (queued)

Dry run mode works every case end to end and records what it would send, sending nothing. CloudWatch alarms and an optional AWS Budget alert are built in.

Edition and proof

HomeNest edition and the hackathon result

3rd place

AWS Communication Developer Services (CDS) Agentic AI Partner Hackathon

Read the hackathon write-up

AWS Select Tier Services Partner

Built and supported by FactualMinds, with 50+ AWS certifications on staff.

See our AWS credentials

No live customer traffic yet. What you can see today: the demo, the guardrail table, and a dry run on your own test orders.

Coming next (not available yet)

  • Shopify adapter and other store connectors
  • One-time code by SMS as a stronger caller check
  • Vision check of photos before a part ships
  • Technician slot booking on the call, with a calendar invite
A modern kitchen with built-in appliances and warm under-cabinet lightingA living room with a grey corner sofa and a low wooden tableReference editionHomeNest, for appliance and furniture retailThe edition built around large items: guided fault help after delivery, spare parts on photo proof and technician requests. It began as the demo store we built for the hackathon; no retailer runs it live yet.See HomeNest

Pricing

Pricing and common questions

CareBridge is priced per deployment and volume. Tell us your order volume and the channels you need, and we send a quote.

Get pricing
Does CareBridge replace my support team?

No. It works the routine follow-up on every order and hands anything it may not decide to your team, with a summary and a link to the case. Refunds always go to a support lead.

Which channels do I need on day one?

One is enough. Email is the usual start. SMS, RCS, WhatsApp and Amazon Connect chat, inbox and phone are switched on as each is approved. A channel that is off gets no permissions.

Can the AI give away refunds?

No. The AI can only request a refund. A signed-in support lead approves or declines it in the console, and the ceiling of 100 in the order’s currency is set in code. Discounts stop at 15% and store credit at 20% of the order, counting everything given on the case.

How do you stop it messaging customers who opted out?

Consent is checked per channel in code before any send. STOP, UNSUBSCRIBE, CANCEL, END, QUIT or a spam complaint opts the customer out of that channel before the agent runs again, whatever the model is told.

Where does my data live?

In your own AWS account. CareBridge is deployed there with AWS CDK, cases are stored in your DynamoDB table, and customer photos sit in a private bucket that deletes them after 30 days.

What if a customer asks for a person?

On any channel, the case moves to that channel’s escalation queue: web chat, WhatsApp, RCS and SMS, email or phone. Your team gets a summary and a link to the full case.

How is CareBridge different from EngageX?

EngageX answers customers who contact you. CareBridge contacts them first, about one order, and follows that order until it is settled.

Which store platforms does it work with?

Any platform that can post a signed webhook to POST /events, plus Amazon EventBridge for delivery events. A Shopify adapter and other store connectors are coming next.

Can we test it without sending anything?

Yes. Dry run mode works every case end to end and records what it would send, sending nothing. Use it before your channels are approved and read the results in the console.

What languages does the phone line support?

The voice agent answers in the caller’s language where Amazon Connect supports that language, using Amazon Nova 2 Sonic speech-to-speech.

How long does deployment take?

It depends on which channels you need and how quickly each is approved. We scope it with you on the discovery call. The dev environment deploys with AWS CDK, and dry run lets you test before channels go live.

Every order gets followed through.

On the channel the customer answers, inside your own AWS account.

  • RCS
  • WhatsApp
  • SMS and email
  • Website chat
  • Support inbox
  • Phone

Photographs from Wikimedia Commons: WillNemoy (CC BY-SA 4.0), Pixel.la (CC0), Shixart1985 (CC BY 2.0), Norbert Levajsics (CC0).