Real answers, built from your real messages.
These are real, unedited answers from SwarmMarshal's assistant — run against a demo mailbox. The people and companies are fictional and no real data is involved, but the work is exactly what it does with your own inbox, chat, and texts: find the evidence wherever it lives, and cite the message behind every fact.
It found the charges in the text messages — on its own.
Nobody told it to look in iMessage. Asked to reconcile recent spending, it recognized the charge data lived in SMS card alerts, opened each one for the exact timestamp, and cited the merchant, amount, card, and time for every charge.
You asked
“Help me reconcile my recent business card spending. What was charged in the last couple of weeks — give me the merchant, amount, which card, and the exact date and time for each — and cite the source for every charge.”
What SwarmMarshal did
On its own, it went to your text messages. In its own words: “The context pack has the card alert messages. Let me read the full details from a few of those SMS alerts to get the exact timestamps.” No one pointed it at iMessage — it knew that's where the charge data lived.
Business card charges — last two weeks (May 12–20, 2026)
| Date & time | Merchant | Amount | Card | Source |
|---|---|---|---|---|
| May 12, 2026 · 2:18 PM | Copper State Office Supply | $143.27 | Visa ending 4821 | iMessage · Fidelity alert |
| May 15, 2026 · 1:46 AM | Sonoran Server Parts | $687.90 | Visa ending 4821 | iMessage · Fidelity alert |
| May 15, 2026 · 1:12 PM | Desert Cloud Backup | $19.95 | Visa ending 4821 | iMessage · Fidelity alert |
| May 18, 2026 · 7:03 PM | Mesa QuickPrint | $58.44 | Amex ending 1006 | iMessage · Amex alert |
| May 20, 2026 · 4:27 AM | Red Rock Hotel Phoenix | $412.08 | Amex ending 1006 | iMessage · Amex alert |
| May 20, 2026 · 4:35 PM | Westbridge Mediation Services | $1,238.60 | Amex ending 1006 | iMessage · Amex alert |
| Total | $2,560.24 |
And it reasoned about what it found
- Flagged that “Fidelity card ending 4821” and “Harborlight Rewards Visa ending 4821” are the same card — same last four, same alert sender.
- Noted it found no card alerts after May 20: “If you made charges between May 21 and today, either the alerts haven't synced or they were sent to a different channel.”
- Offered to cross-reference the early-morning $412.08 hotel charge against travel or event records.
Where the evidence came from
Every row is sourced to an individual iMessage SMS card alert — a different channel from the email receipts in your inbox. In the app, each source is a clickable link that opens the original text so you can verify the exact charge before you trust it.
Captured directly from SwarmMarshal's assistant running against a demo mailbox — fictional people and companies, no real data. The charges, merchants, dates, and times are exactly as the assistant returned them.
Turn a billing dispute into a cited, send-ready email.
Read the whole thread, separate what was admitted from what's still in question, and draft the email — with a citation on every fact.
You asked
“Read all my messages with LedgerCrate about invoice LC-44718. Build an evidence table of the disputed charges and what they agreed to, then draft a send-ready escalation email I can send — with a citation on every fact.”
What SwarmMarshal did
Found the thread, read all five messages end to end, and assembled the evidence below — keeping LedgerCrate's admissions separate from amounts still in question. Every row links back to the exact message it came from.
Evidence table — invoice LC-44718 dispute
| Line item | Original | Disputed? | Resolution | Agreed | Source |
|---|---|---|---|---|---|
| Annual subscription renewal (May 2026–Apr 2027) | $8,400.00 | Yes — duplicate; already prepaid Feb 28 under LC-43102 |
Credit memo CM-2217 issued for $8,400 |
$0.00 | M1, M3, M5 |
| April API overages (original) | $4,038.66 | Yes — usage inflated; CSV mislabeled “archive events” vs billable lookups | Recalculated billable lookups at 365,000 | $1,642.50 | M2, M3 |
Original invoice LC-44718 |
$12,438.66 | — | Voided; replaced by LC-44718R |
— | M1, M5 |
Revised invoice LC-44718R |
— | — | Issued May 13, due May 20 | $1,642.50 | M5 |
What LedgerCrate committed to
| Commitment | Date | Source |
|---|---|---|
| May 14 ACH debit manually cancelled at 2:21 PM Pacific | May 13, 2026 | M5 |
Credit memo CM-2217 for $8,400 issued | May 13, 2026 | M5 |
| Late-fee and service-hold flags removed from the account | May 13, 2026 | M5 |
Invoice LC-44718 voided — do not pay as originally issued | May 13, 2026 | M5 |
Corrected invoice LC-44718R due May 20, 2026 | May 13, 2026 | M5 |
Current status
The dispute is already resolved — LedgerCrate acknowledged both errors, issued the credit memo, voided the original invoice, and cancelled the ACH debit. But the corrected invoice LC-44718R ($1,642.50) was due May 20 and is now 14 days past due as of today. So SwarmMarshal drafted an escalation to confirm account standing before anything else slips.
Draft escalation — ready to send
Dana, Martin, I'm writing to confirm the current standing of our account and invoice LC-44718 / LC-44718R. Summary of agreed resolution On May 12, Dana confirmed that the $8,400 renewal line on invoice LC-44718 was a duplicate, because the February invoice LC-43102 was applied to a legacy customer ID rather than our merged account [M3]. Dana also confirmed that the April overage charge was $1,642.50, not $4,038.66, after correcting the usage calculation [M3]. On May 13, Dana sent credit memo CM-2217 for $8,400 and revised invoice LC-44718R for $1,642.50, confirming that invoice LC-44718 was voided and should not be paid as originally issued [M5]. Dana also confirmed that the May 14 ACH debit for the original $12,438.66 was manually cancelled at 2:21 PM Pacific, the late-fee and service-hold flags were removed, and the corrected invoice was due May 20, 2026 [M5]. Request Please confirm in writing: the current balance due on our account; whether invoice LC-44718R for $1,642.50 remains the only outstanding item; and that no late fees, service holds, or collection actions have been applied since the May 13 resolution. If any balance other than LC-44718R appears on our account, please provide documentation so we can reconcile before payment. Thank you, Sally Russell
Source key — every citation above
| Alias | Message | Date | From |
|---|---|---|---|
| M1 | Past due invoice LC-44718 — account scheduled for debit | May 11, 2026 | Martin Kline |
| M2 | Re: Past due invoice LC-44718 — account scheduled for debit | May 11, 2026 | Sally Russell |
| M3 | Re: Past due invoice LC-44718 — account scheduled for debit | May 12, 2026 | Dana Yu |
| M4 | Re: Past due invoice LC-44718 — account scheduled for debit | May 12, 2026 | Sally Russell |
| M5 | Corrected invoice and credit memo for LC-44718 | May 13, 2026 | Dana Yu |
Captured directly from SwarmMarshal's assistant running against a demo mailbox — fictional people and companies, no real data. In the app, each M1–M5 is a clickable link that opens the original message so you can verify it before you send.
Point it at your real messages.
SwarmMarshal reads your actual email, chat, and calendar history and answers the same way — every fact cited back to the message it came from.