Customer Service When You Are the Department

A Tap and Call customer paid for a Bring Your Own slot, chose to delete their account before setup finished, and might come back later. New Team of One is about the follow-up email that keeps a paying customer out of limbo.

Someone paid for Tap and Call, registered their NFC tag, and then deleted their own account from Settings before setup was finished.

I found out the slow way. Not from a crash report. Not from a dashboard alert. From the order record that outlived the account. They had paid for a Bring Your Own slot. The money was real. They had left on purpose. And if they ever tried to sign up again, I did not want them guessing whether we still owed them anything.

That is customer service when you are a team of one. There is no queue. There is no tier-two. There is you, a paid purchase, and the choice to reach out before someone has to ask.

Delete means delete. That is the point.

Tap and Call has two ways to get a tag working. You can buy a FlairTag, ready-made hardware we ship in the US, or you can bring your own NFC sticker and pay for a registration slot. We added BYO for people who want to use their own tags, or who are not in our shipping footprint. I do not know where this customer lives. I know they chose that path, paid, registered a UID, and did not finish setup before they deleted their account.

Account deletion is also real. People should be able to leave. Tap and Call lets personal users delete their account from Profile. That worked exactly as designed: the login went away, profiles and placements went away, the slot and tag setup went with it. Order records stay, on purpose, for fulfillment and legal reasons. That is not a bug. That is the paper trail.

So this is not a story about a product gap. When you delete, everything tied to you is supposed to go. If the same person signs up again later, they start fresh in the system. That is correct behavior. What I did not want was a paying customer stuck in limbo if they came back and could not tell whether their purchase still counted.

What the follow-up actually looked like

I did not wait for them to open a ticket. I reached out first.

Subject line: We can help you finish your Tap and Call setup.

Plain language. No blame. No "as per our policy." Thanks for trying the product. You bought a BYO slot on this date. Your tag was registered, but you deleted your account before setup was finished. Your purchase is still on file. If you want to pick up where you left off, we can reconnect your slot and tag to a new account.

Then two steps a tired person can actually follow:

Create a new account at tapandcall.com with the same email you used to order.
Reply to the email and tell us you are signed in. We will take care of the rest.

That is it. No portal maze. No "reference number IF-38472-B." Just a human being saying: you paid us, we remember, here is how to continue.

I built the template in the same stack as the rest of Tap and Call's mail: shared branding, clear CTA, reply-to support. The first real send went out this week. When they reply, the reconnect is still manual on my end. Migrate the pending slot, the tag record, the order ownership. Boring backend work. The customer should not have to know any of that happened.

Why this is worth doing even when the product behaved

It is tempting to treat support as the stuff that happens when you are not building. I have done that. It is wrong.

This was not a broken flow I needed to apologize for. Deletion did what it said on the tin. The follow-up was a choice: someone gave us money, and I did not want them wondering if that still meant anything. That is the whole job when you are small. You use the order record you are legally allowed to keep, and you turn it into help instead of paperwork.

Every support email is still a design review you did not schedule. This one reminded me that paid digital goods plus voluntary delete will always have a human moment on the far side. FlairTag orders have a migration script for cases like this. BYO reconnect may get automated someday. For now, a clear email and a willing reply is enough.

That is the solo-builder version of customer service. You do not make the customer prove they deserve help. You assume good faith until you have evidence otherwise. You write like a person because, at this scale, you are the person.

Big companies hide behind process because they have to. You do not have that excuse. Your tone is the brand. A stiff auto-reply from a one-person studio does not read as professional. It reads as absent.

The rules I am trying to live by

These are not revolutionary. They are just easy to skip when you are tired and the next feature is more fun.

Paid beats limbo. If money changed hands, do not leave someone wondering whether it still counts. A row in DynamoDB is not the same as an answer.
Say what happened in plain English. "You deleted your account before setup finished" beats "we are unable to locate an active user entity."
Give one path forward. Two steps. Same email. Reply to this thread. Do not make them hunt.
Separate policy from help. Yes, delete clears the account by design. Yes, orders are retained for legal reasons. Neither of those is a reason to ignore a buyer who might come back.
Reach out before they have to chase you. Proactive beats reactive, especially when the product did exactly what it was built to do.

None of this scales to a million users without systems. I am not there. You might not be either. At this size, how you answer one email is still part of the product.

The part I keep coming back to

The customer did not owe me patience. I owed them clarity because they had already paid.

Sending that follow-up took less time than I spent worrying about whether I should. The hard part was not fixing anything broken. It was deciding that "delete means delete" does not have to mean "good luck figuring out what you bought." Sign back up. Reply. We will take care of it.

That is customer service when you are the department. Not a ticket closed. A person un-stuck.

That's the reality of being a team of one.

#TeamOfOne #BuildInPublic #CustomerService #IndieHackers #TapAndCall