Use cases
Draft support replies from ticket context, with customer details swapped out.
Paste the ticket. Hushbridge swaps the customer’s contact details on your device. The AI drafts the reply, and the real details come back in your draft.
The task
A ticket arrives with the customer’s name, email, phone and shipping address at the top. You want a warm, accurate reply that solves the problem on the first try.
The AI needs the problem and the outcome the customer wants. It does not need their address or phone number to write a good answer. With placeholders, the reply can still greet the customer by name once it is restored.
Before and after
We ran a fictional ticket through the Hushbridge engine with its general profile. The right column is the engine’s real output, unedited.
Fictional example
What you start with
Customer: Marcus Leland Email: marcus.leland@example.com Phone: (503) 555-0117 Shipping address: 218 Alder Court, Apt 3B, Portland, OR 97205 Order 48213 arrived with a cracked lid. He wants a replacement, not a refund. Draft a friendly reply that confirms the replacement and asks for one photo of the damage.
What the AI receives
Customer: [PERSON_1] Email: [EMAIL_1] Phone: [PHONE_1] Shipping address: [ADDRESS_1] Order 48213 arrived with a cracked lid. He wants a replacement, not a refund. Draft a friendly reply that confirms the replacement and asks for one photo of the damage.
- Names
- 1
- Email addresses
- 1
- Phone numbers
- 1
- Street addresses
- 1
Restoring the placeholders on the device gave back the original text exactly in this run.
What you review before sending
- 1Check order, ticket and invoice numbers. In the example, "Order 48213" stays in the text because order numbers are not detected.
- 2Look at free-text notes from the customer. People often add a neighbor’s name, a gate code or a second phone number.
- 3Check any internal notes pasted with the ticket, such as agent names or account flags.
- 4Make sure the reply you ask for does not need the real address. If it does, add the address after the draft comes back.
- 5Read the restored reply before you send it. Confirm the greeting and any contact details are right.
Limits
- Detection uses rules, checksums and name lists. It has no language model. A name with no cue, such as a title, a role or a label, can be missed. Add names you know matter to your always-protect list.
- Order numbers, tracking numbers and ticket IDs are not detected. Add known values to your always-protect list or remove them before you send.
- Context can still identify a customer, such as a rare product and a small town together.
- The browser extension does not scan attachments. Paste the text you want help with into the prompt, and review it there.
- A chat site's page can read text while you type it, before anything is swapped. For sensitive work, prepare the text in the free check first, then paste the protected version into the chat.
- Addresses are found in US style only. Customer names in non-Latin scripts are not covered.
- Review before sending stays necessary. Hushbridge shows you what the AI will get. You decide whether it is safe to send.
Try it
The free check opens with a support ticket example. It runs in your browser and sends no text to an AI model.