- Do the My World deploy on the laptop first, log in, open My relay keys.
- Never type a key. Scan the QR with this phone's camera, then long-press each value to copy.
- Paste your two keys in the boxes below on this page first — every code box then fills itself in.
Profile 1's trigger must be Phone → Received Text and nothing else.
- Do NOT use AutoNotification, AutoInput, or any "read my notifications" trigger — that is what made the bot reply to people over and over. It re-fires on old and duplicate messages.
- Turn the phone's own auto-reply OFF: Messages app auto-reply off, and Driving Mode / Do Not Disturb auto-reply OFF. Those reply on top of the bot.
- No Repeat on Profile 1. No Cooldown that re-runs it.
If it ever double-texts, it is one of the above — not the bot. The server now blocks duplicate replies as a backstop, but keep the phone clean.
0 Put your keys in
Paste from the QR pack. Nothing leaves this page — it only fills in the boxes below.
1 Profile 1 — she gets a text, bot replies
This is the whole conversation. Set it up exactly.
Type: SMS. Leave everything else blank. Back out → New Task → name it Bot Reply.
Action 1 — tap + → Net → HTTP Request. Fill in these four fields:
%SMSRF and %SMSRB are Tasker's own — leave them exactly as written.
Action 2 — tap + → Phone → Send SMS:
2 Profile 2 — messages we queue for her
Alerts and follow-ups the system sends out. Separate from the conversation.
Back out → New Task → name it Bot Outbox.
Action 1 — Net → HTTP Request:
Action 2 — Phone → Send SMS:
3 The one switch people get wrong
Left on, two texts arriving together talk over each other and she looks like she has amnesia.
Now test it
- From a different phone, text her number: hi are you free tomorrow
- You should get a reply back in a few seconds.
- Then text a second one: what about the price
- The second reply must remember the first. If it answers like it has never met you, tell me — that is the old goldfish bug and it means the key or the profile is wrong.