Every channel is set up inbound-only, so the agent never introduces itself

The shape of what is there

/account has a section per channel and every one of them asks the same question: prove this is yours, so we will listen to it.

• Phone — verify a number, then "A text from here reaches your agent, and it answers."
• Email — verify an address, so you may post.
• Mail client — IMAP, so you can read what arrived.
• Push — a toggle in the inbox.

All inbound. Nowhere on the page is the instance's own number or address given to you, and nowhere do you say which of your addresses it should write to. The product's whole claim is that the agent works while you are not looking — which is outbound — and the settings model the opposite direction.

Where it shows

service/sms/verify.go:

send(number, "Your code is "+code+". It is good for ten minutes.")

That text is anonymous. Somebody receives a code from a number they do not recognise, nothing in it says who sent it, and afterwards nothing has told them they can reply to it. So the one message guaranteed to reach a new user — the one they are waiting for, with their attention on it — spends itself on six digits.

The flip

The first outbound message is the setup. It does three jobs at once and currently does none of them:

1. Verifies — the code still travels
2. Delivers the contact — a number that says who it is gets saved; every phone offers "add to contacts" from a message
3. Teaches the interaction — "reply to this and I will answer" is the entire product, learned by doing it once

So: "Your code is 481920. I'm Micro, your agent at micro.mu — reply to this any time and I'll answer."

Same message, same cost, and at the end of it the agent is in the address book instead of being an unknown number.

Scope

• The verification text says who it is from and that a reply reaches the agent
• The same for email verification — the address it comes from should be the one that works, not a no-reply
• Once a channel is verified, the agent sends a first message on it: "this is me, here is what I can do". The moment a channel opens is the moment to demonstrate it
• /account shows, per channel, both directions — what reaches the agent, and what the agent uses to reach you — with the outbound half switchable
• Offer the agent as a contact: a vCard on /account, or an address block that can be copied. For a person who wants it saved deliberately rather than by keeping a text

Not this

Marketing. A second message that says nothing new is worse than no message, and the value here is entirely that the first one is arriving anyway.

Related

• #1481 Gmail and #1482 WhatsApp — both are new channels, and both should be introduced this way rather than configured
• internal/push — a device that has just subscribed is the same moment, and its first notification should be the agent saying hello rather than silence until something happens

Start with /account, service/sms/verify.go, and internal/push, then trace how email verification and channel setup are represented. Compare the inbound-only settings and verification message with the requested outbound directions, introductions, contact details, and first-message behavior across channels. Done means the scoped channels explain both directions and introduce the agent at verification or subscription.