KoltrixCustomer Loop: Where Replies to Your Receipts Should Go
Customers reply to receipts and password resets all the time. Customer Loop threads those replies into your team inbox under the message that caused them.
On this page(7 sections)
Your product sends thousands of emails nobody expects a reply to: receipts, password resets, "your export is ready." Customers reply to them anyway, because replying is the most natural thing to do with an email when you have a question. At most companies, those replies go nowhere. Customer Loop is how Koltrix makes sure they reach a person.
The problem: transactional email is a one-way street
The classic setup splits email in two. Your team uses a mailbox provider for human conversations, and your application uses a transactional email API to send automated messages. The two systems don't know about each other.
So what happens when a customer replies to a receipt?
- If it came from
noreply@, the reply bounces or disappears. - If it came from a real address with no mailbox behind it, the reply disappears without even a bounce.
- If it came from an address that forwards somewhere, it lands in someone's inbox with no context. Which receipt? Which account? What did we send them?
Those replies are often the most important messages a customer sends: "I was charged twice," "this reset link doesn't work," "I didn't sign up for this." Losing them doesn't feel like a problem until it shows up as a chargeback or a cancellation.
How Customer Loop works
Every message Koltrix sends carries a signed reply address that points back to your workspace. When a customer replies to it, three things happen:
- The reply arrives in your team inbox, not in a black hole and not in one person's personal mailbox.
- It's threaded under the exact message that caused it. Whoever opens the reply sees the receipt or reset email the customer is responding to, without searching.
- The customer's other mail with you is on the same timeline, so the support person sees the whole relationship, not just this one exchange.
There's nothing to configure per email. The reply address is added when the message is sent, and it uses your own sending domain, so customers see a reply address that matches the company that emailed them.
Why the reply address is signed
A simple way to build this would be a reply address like reply+12345@yourdomain where 12345 is the message ID. The problem is that such an address is guessable. Anyone who can count could send mail to reply+12346@ and have it attached to a different customer's thread. That makes an unsigned token an oracle for attaching mail to threads you don't own.
Koltrix signs the token, so a reply address can't be forged or guessed. Mail only threads under a message if it came back to the address that message actually carried.
Unsubscribes and suppression
Some replies to automated mail are just the word "unsubscribe." A reply that says only that suppresses the address automatically, so the customer doesn't have to find a link or wait for someone to process it by hand. Hard bounces and spam complaints suppress addresses automatically too. Nobody has to decide.
What changes for your team
The practical effect is that a whole category of support friction goes away.
You stop asking "which email are you replying to?" The thread already shows it. For a billing question, the receipt is right there. For a login problem, the reset email and its timestamp are right there.
Replies reach the team, not an individual. Because replies land in the shared inbox, whoever is on duty sees them. Nothing sits in an ex-employee's mailbox or a forwarding rule nobody remembers creating.
You find out what's confusing. Replies to automated mail are unfiltered feedback. If ten people reply to your trial-ending email asking what happens to their data, the email isn't clear enough. You only learn that if you see the replies.
Where it helps most
| Email type | Typical replies | Why threading helps |
|---|---|---|
| Receipts and invoices | Double charges, wrong company name, refund requests | The exact charge is attached to the conversation |
| Password resets | Link expired, didn't request this, still locked out | Support can see when the reset was sent |
| Onboarding emails | Setup questions, "does this integrate with..." | Early product feedback reaches the people building it |
| Trial and billing notices | "What happens to my data?", "Can I extend?" | Questions arrive while the decision is being made |
| Account alerts | "Was this me?", "How do I turn this off?" | Context for security-sensitive conversations is preserved |
We use this ourselves. ReminderIt, our other product, sends its reminders, receipts and support replies through Koltrix, and replies to those automated messages land threaded in the team inbox. We wrote up that setup in how we send ReminderIt's email.
What you should still do
Customer Loop handles the plumbing, but a few practices make it work better:
- Write automated emails that invite replies. End onboarding emails with a question. Tell customers they can reply to a receipt with billing questions.
- Decide who watches the replies. They arrive in the team inbox, and someone has to own answering them, with the same expectations as any other support mail.
- Stop using
noreply@as your from address. It discourages the replies you now have a place for. Send from a real address likehello@orbilling@instead. - Read replies for patterns. A recurring question in replies to one email is a sign that email needs rewriting.
How it fits with the rest of Koltrix
Customer Loop is one of the reasons Koltrix puts the team inbox and the sending API on the same domain, under one workspace. Your product's email and your team's email share one set of DNS records, one reputation and one place where conversations live. If you're comparing this with a send-only API, our Koltrix vs Resend and Koltrix vs Postmark pages are explicit about when a dedicated sending service is the better choice.
Key takeaways
- Customers reply to transactional email. Without a destination, those replies are lost.
- Every message Koltrix sends carries a signed reply address, so replies land in your team inbox threaded under the original message.
- The token is signed to prevent anyone from guessing an address and attaching mail to someone else's thread.
- "Unsubscribe" replies, hard bounces and complaints suppress addresses automatically.
- Write automated emails that welcome replies, and give someone the job of answering them.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
