Sender setup and reconnects

1. Prepare the email domain

Use the domain setup offered by your account. Existing connections appear under Sending domains. Managed domain requests are available only where enabled; the purchase screen shows price, setup progress and any failure. A request is not a ready sender.

After attaching a domain, setup reads its nameservers and names the DNS host. Where that host offers an API (Cloudflare, GoDaddy, Namecheap, AWS Route 53, Vercel, Google Cloud DNS, DigitalOcean, Netlify, IONOS, Name.com, Porkbun, Gandi, Hetzner, OVHcloud, DNSimple, Linode, Vultr, NameSilo and DreamHost), paste one credential with DNS edit rights and the records are added for you, then verification runs. The credential is used for that request and is not stored. Existing records are left in place. Hosts without an API, such as SiteGround, Squarespace and Wix, get a direct link to their DNS editor with each value ready to copy.

For DNS you add by hand, copy the exact host names and values shown by setup. Verify SPF, DKIM and DMARC alignment with the sending configuration. Do not create duplicate SPF records or guess values. Allow DNS propagation, then run the offered verification check until the domain is ready.

2. Configure the mailbox and identity

Under Mailboxes, set the from-address, sender name and sending pace for a verified domain. Review the workspace postal address, timezone and sending window. A healthy domain alone does not prove that a particular mailbox is ready. Check the mailbox status and ramp before activating a campaign.

3. Connect LinkedIn when needed

Use the LinkedIn connection control and finish any account verification or challenge it shows. LinkedIn outreach waits for contact intent; opens alone do not qualify. Prospect sourcing is also available through the configured prospect service, so it is not dependent on LinkedIn alone.

Repair a connection

Open the sender row and read the status detail. Reconnect through the available control if authorization expired; complete any provider challenge on the owned account. Check assigned workspace, sender identity and daily allowance after reconnecting. If a domain fails verification, correct the shown DNS records and retry verification. Reconnecting does not override campaign pause, budgets, suppression or sending hours.

Confirm the path before expanding

Use controlled recipients to confirm receipt, an inbound reply and opt-out handling. Check the Inbox thread and sender status. Contact support@trygtm.com with the workspace and sender identifiers if setup remains blocked. Do not include credentials or prospect message content in a support request.

Google/Microsoft mailbox OAuth and SMS are separate capabilities. Their presence in the API does not mean they are available in your sender setup; use only the options offered in your account.

SMS is temporarily disabled. When it returns, it runs on your own Twilio, Telnyx or Plivo account: you own the number, its carrier registration and compliance for every text it sends.