Google Play ↗What to know
- Type text sends supported US-layout characters, with up to 500 characters per step; it is not Unicode clipboard transfer.
- Keep reusable wording separate from personal customer details and account credentials.
- Start with draft-only actions. The phone cannot read a ticket, choose the right answer or confirm a message was sent.
Before you start
Connect a compatible Android 9-or-newer phone to a computer that allows Bluetooth keyboard input. Check the host layout and selected Shortcut keys setting.
Start in a disposable document. Check whether Enter inserts a newline or sends a reply in your real support application.
How to do it
Write a neutral reusable line
Choose a short US-layout line such as Thanks for the details. Avoid private customer information and promises that need individual approval.
Make a draft-only text button
Choose Buttons, Edit and a slot. In Tap, add Type text and enter the line. Label it for its purpose, choose Save and then Done. Do not append a send key to the first version.
Check every typed character
Focus the empty test document and tap once. Inspect punctuation, spaces and line breaks under the actual computer keyboard layout. Unsupported characters are not a reliable way to type CJK, emoji or accented text.
Try one unsent support draft
In a test reply field, check focus and insert one line. Review it before sending manually. Save the working profile and revisit the wording when your support policy changes.
A first support-reply board
| Label | A short draft-only example |
|---|---|
| Acknowledge | Thanks for the details. |
| Ask for steps | What steps led to the issue? |
| Ask for version | Which app version are you using? |
| Close politely | Thanks for your patience. |
| Follow-up draft | I will review the information you provided. |
Typing a reply is not deciding a reply
These are starting lines, not automatic answers. Adapt them to the conversation and your support policy. A button cannot check whether a detail was already provided.
Name each button for its purpose. Keep refunds, account changes and other consequential actions separate from text insertion.
Keep sensitive details out of reusable text
Store generic wording rather than passwords, recovery codes or private customer records. If you export or sync a deck, those stored text steps can travel with it, so review the backup contents as part of your normal data handling.
For multilingual support, keep your usual computer input method available. This feature does not provide direct CJK or emoji transfer, variable substitution, ticket-system integration or automatic personalization.
Limits to keep in mind
- Every text action depends on the focused field, keyboard layout and supported characters.
- Do not put secrets or private customer data into a shared deck or reusable text example.
Questions and answers
Can this automatically answer my support tickets?
No. You choose a button, check the focused field and review the draft. The app does not inspect tickets or select answers.
Why keep sending separate from typing?
Reply fields differ in how they handle Enter and shortcuts. Reviewing the inserted text before a manual send reduces the chance of sending the wrong wording or a partial reply.