FINANCE

Draft and Send Proration Over-Billing Correction Emails

For each confirmed over-billing credit, an agent drafts a clear, customer-specific apology email explaining the proration error and the credit applied.

CategoryFinance
Enginepaperclip
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerConfirmed over-billing credit memo
  • ActionPull plan change and credit details from StripeStripeStripe
  • ActionAgent drafts customer correction email
  • LogicReviewer approves or edits draft in SlackSlack
  • OutputSend correction email via GmailGmailGmail

What it does

Once finance confirms a customer was over-charged on a mid-cycle change, this workflow handles the customer communication. An agent reads the credit-memo record, writes a plain-English email that names the plan change, states the corrected amount and the credit applied, and avoids billing jargon. A human approves before anything sends.

When to use it

Use it when over-billing corrections are frequent enough that hand-writing each apology is a drag, but the message still needs to feel human and accurate. It turns a reconciliation record into a trustworthy customer touchpoint instead of a silent credit the customer never understands.

How it works

  1. 1A confirmed over-billing credit memo (from the review queue) triggers the run.
  2. 2The agent pulls the customer, the specific plan change, the billed vs correct amount, and the credit applied.
  3. 3It drafts a concise correction email tailored to that customer's situation.
  4. 4The draft is posted to Slack for a reviewer to approve or edit.
  5. 5On approval, the email is sent to the customer via Gmail and the send is logged on the memo record.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect GmailRead, draft, send, label.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.