Skip to content
KastProductions

An agent that works last night’s failed payments.

Every charge Stripe failed overnight comes back as one summary, with a drafted message per customer waiting in your outbox. Nothing reaches a customer until a named person approves it.

What the agent does

It acts behind an approval gate. Reading Stripe, sorting the failures and writing the drafts needs nobody, and every draft then stops.

  • Reads the night’s failures

    The failed charge itself wakes the agent. It reads the amount, the reason the card gave, the invoice behind it and how long that customer has been paying you.

  • Sorts them by what went wrong

    An expired card, a bank that declined once and a subscription on its fourth retry are three different messages. The agent groups the night before it writes anything.

  • Drafts one message per customer

    Each draft names the invoice, the amount and the next retry, in the wording your team already uses. They wait in your outbox, unsent.

  • Reports the night in one place

    One summary in the channel your finance team already works in: how many charges failed, how much is waiting, and which drafts need a name.

The gate sits before a message leaves your company. A follow-up reaches your customer, so a named person reads it and sends it.

What it touches

Your agent works in the systems your team already pays for. We connect it to each one, and the spec names every account it needs before you commit to anything.

  • Stripe

    The event that wakes the agent, and where it reads the failed charge, the decline reason, the invoice and the retry schedule.

  • Your outbox

    Where every draft waits, under the address your customers already hear from. The agent writes the draft and stops there.

Where your agent lives

A person addresses your agent by name in a chat channel. A system wakes it with an event. Both lists are what Flue verifies, so you can check them.

A person reaches it in

  • Slack
  • Microsoft Teams
  • Discord
  • Telegram
  • WhatsApp
  • Google Chat
  • SMS through Twilio

How an agent works in Slack

Teams needs one step that Slack does not: an Azure Bot registration and an app password stored in your project. We do that work and quote it as its own line.

An event wakes it from

  • GitHub
  • Linear
  • Notion
  • Stripe
  • Shopify
  • Zendesk
  • Intercom
  • Resend
  • Salesforce Marketing Cloud

What it costs

A job we have not built before is custom work, so this one is priced at the custom door. The numbers below are floors: we read your workflow first, then name one fixed price.

Custom agent

You describe this job as your company runs it. We write the spec, name the price, and build the agent around it.

From €10,000 to build
From €1,500 a month to operate

The door says what a custom agent needs from you, and what the month after it goes live buys. How a custom agent is built