The Header
Add one of the following headers to the SIP INVITE sent to Telzino (both spellings are accepted):Supported Value Formats
Extension Format
extension@host, Telzino resolves the extension to a person using your PBX directory (for example, via the NetSapiens integration) or the agent’s saved message-taker directory. This yields the person’s display name and email address.
If your agents are deployed through Telzino Connect on a NetSapiens platform, this header is attached automatically when a user’s call is forwarded to your agent — no extra configuration is needed.
Free Text
What the Agent Does With It
Greeting Personalization
-
If your agent’s greeting contains the
{name}placeholder, it is replaced with the resolved name. -
If the greeting has no placeholder, the agent prepends an introduction:
- If the resolved name matches the agent’s own name (for example, the header carries the agent’s own PBX extension), the greeting is spoken unchanged — the agent will not announce itself as its own assistant.
In-Call Context
The agent is informed that the call was originally dialed for the resolved person and that it is answering on their behalf. If an email address was resolved, the agent sends the message summary email to that address. When a caller asks who the agent is taking a message for, it answers with the resolved name.Adding the Header From Your PBX
Most SIP platforms can add custom headers on the leg that forwards the call to Telzino. For example, in an Asterisk dialplan:Behavior Notes
- The header value is always treated as data about the call — never as instructions to the agent.
- If the value cannot be resolved or parsed, the call proceeds normally, exactly as if no header were present.
- Extracted names and email addresses are validated and sanitized before use.
