Sent History is the fourth and final card on the Auto Messages page. It's a running log of every automatic message Teddy has actually sent out on your behalf — every After Call Text, every Upcoming Appointment Reminder, every Birthday Notification, and everything in between.
Where the other Auto Messages categories are about configuring reminders, Sent History is about verifying them. It answers the question: "Did that text actually go out?"
Each row in Sent History is one automatic send. The columns are:
Information — the reminder name (e.g. "After Call Text," "Appointment Scheduled," "Upcoming Appointment Confirmation")
Client Name — the client the message was sent to (or their phone number if they're not a registered client)
Method — sms or email, showing which channel the message went out on
Date & Time Sent — the exact timestamp of the send (format: MM-DD-YYYY HH:MM AM/PM)
Rows are sorted newest-first, so the most recent send is at the top.
A few real rows to show you what this looks like:
After Call Text → 2083773800 → sms → 04-10-2026 01:47 PM (The After Call Text fired seconds after a call from 208-377-3800 ended at 1:46 PM yesterday.)
Upcoming Appointment Confirmation → pablo monte → sms → 04-10-2026 09:32 AM (Pablo was sent an Unconfirmed-status confirmation request for his upcoming appointment.)
Appointment Scheduled → pablo monte → sms → 04-10-2026 09:30 AM (Two minutes earlier, Pablo was notified that his appointment had been scheduled — so in sequence: Scheduled → wait → Confirmation request.)
You can read a client's entire auto-message history by scanning for rows with their name.
Most of the time you won't. But Sent History is the first place to go when something seems off:
"Did my client get the reminder?" — Search this list for their name. If the row is there, yes. If it isn't, no.
"Why is a client saying they got double-texted?" — You'll see both sends here with timestamps. Sometimes it's a legitimate second reminder; sometimes you'll spot a duplicate that points to a config issue.
"I turned off that reminder, why is it still going out?" — Check the recent rows. If the reminder name still appears after the time you toggled it off, the toggle didn't save (go back and re-check the Auto Messages category).
"A client says they got an auto-message about an appointment I cancelled." — Check the timestamp here against when you cancelled; sometimes the reminder fires in the minutes between cancellation and the next send cycle.
Sent History only shows automatic sends — messages Teddy fired on its own. Manual messages (the ones you typed and sent yourself from the Messages page) don't show up here. If you want to see everything that's been sent to a client, automatic + manual, open their conversation thread in the Messages tab — all messages of both kinds show up there in the normal chronological order.
Likewise, Sent History shows messages sent, not messages delivered or read. A row here means Teddy handed the message off to the SMS provider successfully. If the client's phone was off or their carrier was having issues, the message could still have failed to land even though it's shown as sent here. For delivery issues, check the client's thread in Messages for any error indicators or check with your SMS provider through support.
Sent History can grow long quickly — a busy shop can accumulate hundreds of automatic sends per week. The page uses standard pagination at the bottom. There's no in-page search, so if you're looking for a specific send, use your browser's Find-in-Page (Ctrl/Cmd+F) on the name or date.
Sent History is scoped to your shop — you only see your own sends. Other Teddy shops can't see anything here.
There's no documented retention limit on entries; in practice the log goes back indefinitely, which means it's a useful audit trail if you're ever asked to prove that you did notify a client about a cancellation or appointment change.
Tip: If a client ever disputes whether they got an auto-message, screenshot the relevant Sent History row as a record. The row shows the reminder name, the client, the channel, and the exact timestamp — which is usually enough to resolve the dispute.
