Answers, and an assistant that never sleeps.

Reviewed September 7, 2026, covering July 27–September 7. Seven16 Email now connects the complete campaign: goal, audience, message, assets, intentional publication, capture, reporting, and reviewed follow-up. - Campaign assets: Landing Pages, focused Campaign Sites, version history, custom-domain checks, forms, files, tracked links, QR codes, and channel attribution share a Marketing Studio campaign. - Audience and relationship tools: self-updating segments, custom fields, policy and renewal workflows, cross-sell gaps, unified contact history, and one-to-one Sendblue texting. - Surveys: relationship and external-marketing templates, versioned scoring, response reporting, and producer follow-up tasks. The newer Signal Survey intelligence extension is awaiting production rollout. - AI: source-backed Landing Page proposals and evidence-gated experiments; an OAuth MCP private pilot for campaign analysis and reviewed connected drafts. These are separate from the read-only Ask AI help widget. - Operations: living deliverability policies, domain portfolio readiness, retained consent evidence, stronger suppression checks, and delivery-state reconciliation. - Account controls: workspace switching, authenticator MFA, data recovery/retention controls, and verified Network evaluation and private pricing alongside the standard retail trial. - WorkComp Finder: live retail and wholesaler discovery paths, plus a controlled communications integration. Broad automatic contact transfer and sending are not generally enabled. Availability matters: MCP remains an allow-listed private pilot; reply intelligence has a separate feature gate; API access is team-provisioned; the Node SDK source is available but is not published to npm. See the related articles before assuming access in your workspace.

Seven16 Email is the commercial-insurance campaign operating system: email, Landing Pages, focused Campaign Sites, forms, graded surveys, insurance-aware relationship data, reporting, and reviewed AI assistance in one connected campaign. The workflow is Goal → Audience → Message → Assets → Publish → Capture → Learn → Follow Up. Build the campaign, not the plumbing. Email starts the conversation; a page, form, or survey captures the response. Reporting connects the assets so follow-up is based on evidence. Quote, bind, and premium attribution requires actual outcomes supplied by a connected system. It is built for retail agencies, producers, wholesalers, MGAs, MGUs, and program teams working on renewals, cross-sell, appetite updates, and partner recruitment. It is not a generic website CMS, a replacement for your agency management system, or an unrestricted cold-blast service. See the complete-campaign quickstart and the WorkComp Finder connection guide for practical examples.

1. Sign in with Google or a magic link at the sign-in page. 2. First-time users are taken to onboarding to name their workspace (your agency's space for contacts, campaigns, and sending). 3. Name your workspace, then pick a plan to start the 7-day free trial. You enter a card, but you're charged $0 that day — billing only begins when the trial ends, and cancelling before then costs nothing. Your trial runs at the full limits of the plan you chose. If you cancel, or the first charge fails, the workspace switches to read-only until you choose a plan; your contacts and data are always safe and exportable.

Ask AI on the website and inside the app is a read-only product guide grounded in this Help Center. It can explain features, give menu paths, distinguish relationship surveys from external-marketing surveys, and help you choose a documented workflow. It cannot see contacts, campaigns, messages, payment details, or another workspace. It cannot send, launch, change settings, or claim it completed an action. Never give it a password, API key, card number, or other secret. For a real account change, use your own authenticated Settings page. If the Help Center does not verify an answer, the assistant should say so and direct you to support@seven16email.com instead of guessing.

Start with one commercial objective: an appetite update, renewal conversation, workers' comp inquiry, or retail-agent recruitment campaign. 1. Open Dashboard → Marketing and create a campaign for that objective. Choose a permission-eligible audience and a verified sender. 2. Prepare the email and attach the supporting assets to the Marketing Studio campaign. Use Landing Pages for the destination and Forms for the response. Add a survey or file when it helps the visitor take the next step. 3. Review the message, source facts, brand, mobile preview, form fields, consent wording, thank-you destination, and CTA. Keep sensitive applications and loss information in the approved secure submission channel. 4. Activate the form and publish the reviewed page intentionally. A saved draft is not a live destination. Put the final published page or tracked link in the email and test the full path. 5. Run audience, consent, suppression, sender/domain, quota, and content-readiness checks. Sending is a separate deliberate action. 6. Open the campaign's asset and funnel reporting to inspect visits, valid submissions, and attributed engagement. Review a follow-up recipe or assign a producer task. Success means a visitor can follow the final link, submit the intended form, reach the thank-you experience, and appear in the correct campaign reporting. A quote, bind, or premium outcome appears only when a connected system supplies that outcome.

Dashboard → Marketing → Landing Pages builds focused pages from supported sections, brand assets, forms, surveys, files, meeting links, and CTAs. Campaign Sites group a small set of pages for one campaign; they are not a full corporate website CMS. Save and preview privately first. Publication creates an immutable version: editing the draft does not silently change the live page. Review version history and comparisons before publishing a revision. Scheduling, cloning, archiving, and slug redirects help manage the page lifecycle; check the current status and destination after each change. A campaign-site custom domain must pass ownership, DNS, and security checks before serving the site. Website-domain readiness is separate from email-domain authentication. Follow the records shown by the product rather than replacing your normal mailbox records. Tracked links and downloadable QR codes identify the campaign/channel that brought a visitor. Test the final published destination on a phone as well as a desktop. Anonymous visits and clicks are analytics, not permission to contact a person.

Go to Dashboard → Campaigns → New. 1. Name the campaign (internal only). 2. Choose the audience: a saved list or one or more tags. Suppressed, unsubscribed, and bounced contacts are filtered out automatically. 3. Set the sender (a verified sender identity) and subject line. 4. Write the body. Use merge fields (chips like {{ first_name }}, {{ company }}) to personalize; a compliance footer with your address + unsubscribe link is added automatically for marketing sends. 5. Pick the send type / purpose (marketing, operational, or transactional) — this drives which compliance rules apply. 6. Review the pre-send checks (verified sender, filtered audience count, footer) and Send now or Schedule. You can send a test to yourself before the real send, and preview the merged output per contact.

Merge fields insert per-contact data into subject lines and bodies. Insert them from the merge chips in the editor. Common fields: {{ first_name }}, {{ last_name }}, {{ company }}, plus any custom fields you define (Contacts → Custom fields), your own reusable values ({{ values.booking_link }} — see Settings → Your values), and insurance data like carrier or DOT number on DOT-sourced contacts. If a contact is missing a value, provide a fallback so you never send "Hi ,". Always preview before sending — the editor shows the merged result for a sample contact.

A/B testing splits a campaign audience across two or more weighted variants. Each recipient is assigned one variant at launch, and that assignment stays attached to the send so engagement can be compared honestly. For an automatic winner, choose highest open rate, highest click rate, or highest conversion rate before launch. Seven16 waits at least 48 hours and verifies that no sends are still queued or processing. It then compares unique engaged sends divided by sends for each variant. Conversion rate uses connected outcomes that can be attributed to a specific send. A tie stays a tie — Seven16 does not manufacture a winner. Manual strategy leaves the decision to you. Open-rate winners are directional because Apple Mail Privacy Protection can prefetch tracking pixels. Click rate and connected conversion rate are stronger decision signals. The campaign page shows the chosen metric, winning rate, and margin after settlement.

Not yet, and that's on purpose rather than an oversight. Email HTML renders inconsistently across Outlook, Gmail, Apple Mail, and mobile clients — a real drag-and-drop canvas needs a purpose-built rendering engine underneath it, or it produces broken layouts the moment someone opens it in Outlook. We'd rather ship that properly than ship a canvas that breaks. What you get today instead: - 72 Done-for-You commercial-insurance campaigns — 40 coverage-specific renewal/service messages, 16 account-rounding messages, and 16 retail-agent appetite/capability messages — plus utility and DOT-specific outreach starters - An AI writer that drafts a full campaign from one prompt - Merge fields plus reusable "your values" ({{ values.agency_name }}) so you type your agency's details once and reuse them everywhere - Full control of the raw HTML if you or a designer want to build something custom — paste it straight into the editor A richer visual builder — block library, reusable sections, brand kit — is on the roadmap. Templates + AI drafting + merge fields cover how most agencies actually run this today: pick a template, personalize it, send it.

Marketing Studio (Dashboard → Marketing) is the shared workspace for one commercial objective. Attach emails, sequences, Landing Pages, forms, surveys, files, CTAs, and tracking links to the same campaign so their status and performance stay connected. - Landing Pages and Campaign Sites provide the focused destination, with private drafts and immutable published versions. - Forms collect the fields needed for the next step. Explicit consent controls retain evidence when the visitor actually opts in; submitting a form alone is not blanket marketing consent. - Surveys add structured answers, scoring, and reviewed follow-up. - CTAs, files, tracked links, and QR codes connect resources and channel attribution. Create the assets, preview the complete visitor journey, and publish/activate intentionally. Use the final live destination in the email, then verify the link and form before release. The campaign detail screen reports the attached assets and funnel evidence. See the complete-campaign quickstart for the sequence.

Seven16 connects the full Landing Page job without giving automation or AI silent authority. Follow-up recipes: open Dashboard → Sequences. The campaign follow-up recipes create an inactive draft tied to a specific Landing Page response, form, survey, or known tracked-link/QR click. Review the trigger and producer-task steps, then activate intentionally. Anonymous page and link activity stays analytics-only. AI copy and section proposals: open a Landing Page detail screen and add a campaign brief containing only verified facts. The assistant returns structured section proposals plus assumptions, model and prompt-version evidence. Deterministic commercial-insurance checks hold guaranteed outcomes, universal appetite, unsupported carrier/licensing claims, and numeric claims missing from the supplied context. A human must approve before clean sections are appended to the private draft. The page is never published automatically, and a proposal becomes stale if the page changes first. Optimization and experiments: the same Landing Page screen shows human views, valid conversions, attribution quality, and observation days against the workspace's editable evidence policy. You may save an experiment draft at any time, but it cannot start until every active check passes and its control is the current published immutable version. Running experiments assign stable privacy-safe control/challenger variants and preserve version attribution on views and forms. Variant counts remain audit evidence; Seven16 withholds an optimization conclusion until both variants meet the active evidence policy. It never auto-publishes a winner.

Dashboard → Marketing → Surveys provides relationship and external-marketing starters to help a producer ask structured questions about an insurance opportunity rather than build every question from scratch. The newer Signal Survey collection and richer intelligence profiles are awaiting full production rollout as of September 7, 2026. Ask Support which templates are available in your workspace; do not assume the richer profiles are live because a collection appears in a menu. Choose the appropriate audience and copy a starter into your workspace. Review its wording, answer choices, scoring, verified program facts, and requested follow-up before publishing. Keep relationship feedback separate from prospect qualification, and use external marketing only for audiences you are permitted to contact. Published standard surveys show responses and configured scores for a producer conversation. A score is not a coverage decision, quote, guaranteed eligibility, or consent. Review individual responses and the reporting context before creating follow-up work. Ready-made content still needs your review and deliberate publication; it does not launch an outreach campaign by itself.

Seven16 Email has two survey lanes, both built for commercial insurance work. - Relationship surveys start useful conversations with clients, appointed agents, brokers, and other people you already know. - External marketing surveys are industry-specific coverage checkups for prospects you are legally and contractually permitted to contact. The shared library includes Commercial Trucking, Restaurant & Food Service, and HVAC & Mechanical Contractor checkups. A public survey link can be shared through compliant channels, and completed answers produce a consistent score and follow-up context. “External marketing” does not mean purchased or scraped cold lists are automatically allowed. Your sending provider's rules, Seven16 suppression checks, unsubscribe handling, contact purpose, and applicable law still apply. The tenant sending the message remains responsible for having permission to contact that audience.

Each scored survey uses explicit answer weights and result bands, so the same answers produce the same result. The Survey Standard blocks broken scoring such as unreachable or overlapping result tiers before publishing. The score is a conversation signal, not insurance or legal advice. Relationship surveys reveal opinions, friction, readiness, or market sentiment. External-marketing checkups surface class-specific exposures, uncertainty, timing, and buyer intent. Results retain the individual answers and risk flags so a producer can follow up on what the respondent actually said instead of sending a generic pitch. Every completed response creates an in-product notification in Tasks for the workspace owner or admin. A request for a call or resource creates a prioritized human follow-up task; a hot score without a stated request creates a high-priority task labeled as an inference. Nurture responses can enter an active assessment-completed sequence. A respondent who says they are not a fit is never enrolled or assigned a follow-up task, and the notification explicitly says not to follow up. These actions do not send an email or text by themselves.

The Cross-Sell tool (Dashboard → Cross-Sell) turns the renewal and effective-date data you already keep into timed plays to sell another line to an existing client. Each opportunity is a current line → target line pair (e.g., commercial auto → workers' comp) with a 60–120 day outreach window before the target's effective date. - Filter to "In window now" to see exactly who to work this week. - Add opportunities manually, or post them in from your CRM via the API. - Statuses move open → campaign created → converted (or dismissed), so nothing slips through the cracks. Rounding out monoline accounts is the highest-ROI outreach most agencies aren't doing systematically — and the data to do it is already sitting in your book.

To run a cross-sell campaign to your existing clients: 1. Build a list of clients who hold one line but not another — e.g., "commercial auto clients with no workers' comp," or "GL-only accounts." Filter on contact type, lifecycle stage, and tags, then save the result as a list. 2. Time it to the target line's renewal/effective window (60–120 days out) with the Cross-Sell tool. 3. Write to the gap — name the coverage they're missing and the exposure it leaves open, not a generic pitch. 4. Review and activate a short follow-up sequence intentionally. Configure inbound capture so detected replies can stop the follow-up. An existing client relationship does not automatically make a promotional offer operational email. Choose the purpose that matches the message and retain the required permission evidence. Marketing suppression and current sending checks still apply to cross-sell campaigns.

Seven16 keeps human review next to the work in Dashboard → Tasks. Where enabled, a review shows the proposal, evidence, assumptions, and review history so an authorized person can accept, correct, or reject it. Reply and next-action intelligence is separately feature-gated. It is not automatically enabled by connecting MCP or by configuring ordinary inbound reply capture. When available, its job is to explain a reply and recommend a human next step; it does not send a reply automatically. Privacy-minimized outcomes are different from raw message content. Ordinary inbound capture still records replies and can stop configured sequences. An AI interpretation never creates permission, removes suppression, or authorizes outreach. A review decision records what the human decided. Only the specifically labeled Create connected drafts action can materialize the supported private campaign bundle, and publication/sending remain separate.

A sequence is an automated series of emails with delays between them (e.g., Email 1 immediately, follow-up on day 2, another on day 5). Go to Dashboard → Sequences → New. 1. Add steps, each with its own template/content and a delay ("wait 2 days"). 2. Enroll contacts — manually, from a list, or automatically via an enrollment trigger. 3. Turn the sequence on. The send worker runs every minute and sends due steps. Replies exit the sequence automatically so you never keep following up with someone who already responded. The same protection applies when a contact converts: if a quote, bind, or premium outcome is recorded for them (via a connected product like DOT Intel or the outcomes API), their active enrollments exit automatically — you can turn this off per sequence on the sequence page ("Exit rules"). Each step's send is metered against your plan's send quota.

Instead of manually enrolling, you can set an enrollment trigger so contacts join a sequence automatically when they match a condition (for example, a new contact from a given source, or a contact entering a lifecycle stage). New qualifying contacts are enrolled going forward. Replies and unsubscribes remove them from the sequence.

Two ways policy data (Dashboard → Companies → a company → Policies) turns into work that happens automatically or gets surfaced for you. **Automated renewal touches.** Create a sequence (Dashboard → Sequences) with trigger "Policy renewal approaching." Pick how many days before the X-date the first touch fires — 120, 90, 60, 45, or 30 — and optionally narrow it to one line of business. The sequence enrolls the account's contact automatically the day a matching active policy crosses that threshold; later steps in the same sequence land on their own delays, so a 120-day first touch with 30-day steps reaches 120, 90, 60, and 30 days out with no extra setup. When a policy renews and its expiration date moves a year out, the sequence fires again for the new cycle — you don't have to re-enroll anyone by hand. Runs once daily. **Cross-sell gap report** (Dashboard → Cross-Sell → Find gaps): every account holding at least one policy, and which lines of business they don't have, sorted by premium held so the biggest accounts show first. Click "Create opportunity" on any missing line to add it straight to your cross-sell pipeline — no retyping the account or the lines involved. Both read the same Policies data, so keeping policies current (line of business, premium, and the expiration date especially) is what makes both of these work.

Every contact has two independent axes: - Contact type — what the contact IS (e.g., prospect, client, broker, carrier contact, partner). - Lifecycle stage — where they are in your funnel (e.g., new, engaged, opportunity, customer, dormant). Keeping these separate lets you segment precisely — for example, "brokers in the 'engaged' stage" — without one field having to mean two things.

A campaign can use a list, one or more tags, or a saved segment. Lists are curated membership. Tags are reusable labels, and a campaign includes anyone carrying any selected tag. Segments are self-updating rules across contact fields, commercial-insurance company fields, tags, and custom fields—for example, “TX or OK trucking companies with 10+ power units and renewals in the next 90 days.” Build and preview segments under Contacts → Segments. The preview shows the current count and a small sample. Campaign launch re-evaluates the rules, so the audience stays current. Invalid or outdated rules stop the launch; they never fall back to all contacts. Suppression, unsubscribe, bounce, and consent rules are still applied after the segment resolves.

Define your own fields under Contacts → Custom fields (for example, "Producer," "Line of business," or "Effective date"). Custom values can be stored on contact and company records. Supported field types include short and long text, number, yes/no, date, date and time, email, URL, dropdown, and multi-select. Use the field's merge key when personalizing an email. Tags, lists, and the built-in insurance fields remain the simplest tools for building campaign audiences.

Track policies on a company (Dashboard → Companies → open a company → Policies) to power renewal timing, cross-sell targeting, and win-back campaigns. What you can record per policy: line of business (Workers' Comp, GL, BOP, Commercial Property, Umbrella, Business Auto, Commercial Auto/Trucking, Motor Cargo, Professional Liability, Cyber, EPLI, D&O, Inland Marine, Surety/Bonds), status (active, pending, prospect, non-renewed, cancelled, lost, expired), policy number, carrier, wholesaler/MGA, annual premium, effective and expiration dates, and underwriting detail — loss ratio, claims count, open claims, last loss date, experience mod, loss control notes. How each motion uses it: - Renewal — the expiration date (X-date) is what a renewal cadence times against. Set it on every active policy. - Cross-sell — compare the lines of business you hold on an account against the full catalog to see what's missing (a GL-only account with no Workers' Comp, for example). - Win-back — mark a policy status "lost" with who took it, when, and why. That's the pool a win-back campaign draws from, and the timing to reach back out is usually their new carrier's renewal anniversary. Merge fields: campaigns and templates can reference {{ policy.line_of_business_label }}, {{ policy.carrier_name }}, {{ policy.premium_annual }}, {{ policy.expiration_date }}, {{ policy.days_to_expiration }}, {{ policy.loss_ratio }}, {{ policy.experience_mod }}, and more. Each resolves to the account's single most relevant policy — the soonest-expiring active one, or if none is active, the most recently lost one. A blank policy field just means the account has no policy on file yet; it never breaks a send.

DOT Intel is the Seven16 family's trucking/carrier intelligence product. When it's connected, carrier records — DOT number, authority age, fleet/power-unit size, operation type, state, and risk signals — flow straight into your Seven16 Email contacts as a ready-to-target audience, tagged with their source. You don't re-key anything: leads land as contacts with the carrier fields already populated, so you can filter, tag, and personalize immediately. To connect it, go to Settings → Integrations (or ask us to provision it for you). If you don't use DOT Intel yet, you can still import carrier lists by CSV — but DOT Intel keeps them fresh and attributed automatically.

DOT Intel (dotintel.io) supplies carrier and FMCSA intelligence — DOT number, authority age, fleet size, current insurer, X-date — and can push it straight into your Seven16 Email contacts as a ready-to-target list, already tagged by source. Setup is one click from DOT Intel ("Enable Email Campaigns"); no API keys change hands. Everything else you need can come in by CSV import or the REST API. Your CRM or agency management system can post outcomes back so campaigns attribute to revenue.

Two honest answers, and the order matters. Start with the book you already have. Most agencies have far more renewal and cross-sell opportunity sitting in their existing clients than they can work by hand — accounts renewing in 60–120 days, monoline clients who were never asked about another line, brokers who quietly stopped submitting. That's the highest-return outreach available to you and it needs no new data at all. If you need new names, DOT Intel (dotintel.io) supplies trucking and carrier data with insurance-relevant fields. You can also import any list by CSV or API. One important limit: everyone you email must have a business relationship with you or have opted in. Purchased, rented and scraped lists are prohibited — both by our terms and by the sending providers underneath. Capture forms are the built-in way to collect opt-in properly.

A dedicated sending subdomain, such as email.youragency.com, helps separate campaign configuration from your everyday mailbox. It can reduce operational overlap, but it does not guarantee that reputation problems cannot affect the wider domain. Follow the active deliverability policy and the DNS records shown in Settings → Email → Domains. Preserve your existing mailbox records. Choose a monitored sender and set its intended use so marketing and operational communication use the appropriate identity. Review the actual readiness message if a sender does not match the campaign purpose. Authentication, sender suitability, permission, suppression, and current health are separate checks. A second subdomain never authorizes additional volume or bypasses a hold.

To stay out of spam: 1. Authenticate your own domain (SPF/DKIM) before sending real volume. 2. Send to people who expect to hear from you; import clean lists and remove bad addresses. 3. Warm up — ramp volume gradually rather than blasting a cold list on day one. The platform enforces this for you (see "Domain warm-up"). 4. Keep content relevant and include a clear unsubscribe (added automatically on marketing sends). 5. Watch bounces and complaints; suppression handles hard bounces and unsubscribes for you, but high rates hurt reputation.

Settings → Email → Domains shows each domain's current warm-up state and available headroom. The active approved deliverability policy, current domain/provider health, and audience quality govern pacing; a historical stage ladder is not a permanent allowance. 1. Verify the sending domain and review its sender readiness. 2. Check the current domain card and any health or policy warning before scheduling volume. 3. Review campaign audience readiness, suppression, consent evidence, plan allowance, and remaining headroom separately. An intended campaign schedule does not waive these checks. 4. If delivery is deferred by a capacity or health hold, inspect the reason and current status before retrying. Do not create a duplicate campaign to bypass the hold. The domain portfolio adds policy-driven sender readiness, provider/mailbox lane health, history, and alerts. Owners maintain the living policy through categorized intake, human approval, version history, comparisons, and audited rollback. Policy guidance and implemented runtime controls are identified separately. Ask Support when the active policy and observed runtime state disagree rather than assuming an old cap is authoritative.

You can text a contact one-to-one from their contact record, through your own Sendblue account (Settings → Integrations → Texting). Messages go iMessage-first, falling back to RCS and then SMS. How it works: 1. Connect your own Sendblue account — your account, your phone line, your qualification with the provider. You attest at connect time that consent for your recipients is yours. 2. Open a contact and use the Text messages panel. One contact, one message — there is no bulk texting, by design. Sendblue prohibits blasts and so do we. 3. Replies appear on the contact record via the webhook you paste into Sendblue. The rules the platform enforces: - STOP is final. If someone texts STOP, that number is blocked immediately and only the recipient texting START clears it. There is no override. - Sends outside 8am–9pm (your workspace timezone) are held. - Texting consent is separate from email consent — an email opt-in does not carry over to texting.

Seven16 uses guardrails rather than handcuffs. The operating standard separates conditions that must stop, signals that should adapt sending behavior, and recommendations that improve results without becoming universal laws. Thresholds and provider requirements are maintained as dated policy records so the guidance can change without rewriting the product. Hard guardrail Stops only the conditions that can cause serious harm. - Authenticated sending only: Do not send from a domain that has not passed the authentication required for its provider and traffic class. Source: Seven16 Responsible Outbound Operating Standard · verified 2026-08-21 - Honor suppression across every sending lane: A domain, mailbox or campaign change must never bypass an unsubscribe, complaint, hard-bounce or do-not-contact decision. Source: Seven16 Responsible Outbound Operating Standard · verified 2026-08-21 - Human conversation supersedes automation: Pause automated follow-up when a legitimate human reply begins a conversation. Source: Seven16 Responsible Outbound Operating Standard · verified 2026-08-21 Adaptive guardrail Warns, tests, throttles and isolates before a broad stop. - Ramp consistently instead of obeying a magic daily number: Evaluate volume changes against the sender's own history, health, provider mix and campaign risk. Source: Seven16 Responsible Outbound Operating Standard · verified 2026-08-22 - Keep domain and mailbox health separate: Isolate a struggling mailbox or provider lane instead of stopping a healthy domain or tenant without evidence. Source: Seven16 Responsible Outbound Operating Standard · verified 2026-08-21 - Respond to bounce type, trend and sample size: Suppress permanent invalid recipients promptly; retry or defer temporary failures according to provider response. Source: Seven16 Responsible Outbound Operating Standard · verified 2026-08-21 - Treat complaints as an early and serious signal: Warn and reduce affected traffic before provider enforcement thresholds are reached; pause severe or accelerating complaint patterns. Source: Google Email sender guidelines · verified 2026-08-21 - React to the provider lane that is deteriorating: Measure Google, Microsoft, Yahoo and private-domain outcomes independently when evidence supports the distinction. Source: Seven16 Responsible Outbound Operating Standard · verified 2026-08-21 - Score the campaign before scale: Use infrastructure, data, audience, message and sending-pattern evidence to explain campaign risk before launch. Source: Seven16 Responsible Outbound Operating Standard · verified 2026-08-21 - Treat verification and data freshness as context: Strongly encourage verification for cold outbound and learn how source, age, industry and recipient type affect actual bounce performance. Source: Seven16 Responsible Outbound Operating Standard · verified 2026-08-21 Recommendation Improves results without pretending every practice is a law. - Separate transactional, operational and promotional traffic: Use purpose-specific sending lanes so essential messages do not share avoidable risk with prospecting campaigns. Source: Resend domain management guidance · verified 2026-08-21 - Start small and earn scale: Begin with a relevant test cohort, evaluate sender health and business outcomes, then scale the combinations that work. Source: Resend warm-up guidance · verified 2026-08-21 - Optimize for qualified outcomes per healthy delivered email: Measure the complete funnel from valid address through qualified conversation, opportunity, quote, bind and revenue. Source: Seven16 Responsible Outbound Operating Standard · verified 2026-08-21 The North Star is qualified conversations and business outcomes per healthy delivered email—not maximum send volume. A policy record describes operating guidance; the campaign review screen remains the source of truth for which automated checks are active on a specific send.

Every send is classified by purpose, and the platform applies the right rules automatically: - Marketing — promotional outreach. Requires an unsubscribe link and a physical-address footer (added automatically), and respects unsubscribes. - Operational — service/relationship messages to your book (e.g., a broker update or emergency notice). Lighter footer requirements. - Transactional — 1:1 triggered messages (e.g., a receipt). Purpose-specific marketing opt-outs are treated separately; global hard-bounce and complaint suppression still applies, and every send is logged. This purpose-aware model lets you run both everyday communication and prospecting from one platform without tripping compliance.

Seven16's Legal Center is an operating system, not just footer copy. - Public policies come from frozen, versioned publications. An administrator can prepare a later draft without silently changing the live version. - A policy cannot publish until required company facts are verified, placeholders are resolved, effective dates are present, and counsel approval evidence is retained. - The Privacy Request Center (/legal/privacy-request) accepts access, correction, deletion, portability, sale/share opt-out, targeted-advertising opt-out, and appeal requests without requiring an account. - Consent events retain the wording, action, source, time, page, and an evidence hash. Fulfilled deletion or sale/share requests create a global Seven16 Email suppression when an email address is involved. - Data-source rights fail closed: unknown, restricted, internal-only, no-resale, and deletion-on-termination sources cannot be marked as sellable inventory without a supported rights state. These controls help Seven16 and its customers follow a governed process; they are not a guarantee of legal compliance or a substitute for advice from qualified counsel.

Marketing Studio ties asset performance to one campaign: email engagement, page visits, valid form responses, survey starts/completions, file or CTA activity, and tracked-link/QR sources. Provider acceptance and confirmed delivery are separate events. The platform reconciles provider callbacks with campaign and contact/send status; acceptance alone is not proof that a person received or read the message. If a record appears stuck, compare its delivery evidence and timestamps before retrying. Ask Support to investigate uncertain delivery rather than launching a duplicate. Known activity can retain the campaign and contact attribution established by an authorized send. Anonymous traffic remains analytics-only. Connected quote, bind, and premium reporting requires actual outcome records from the originating system. Landing Page experiments wait for the active evidence policy's views, conversions, attribution quality, and observation period. Saving an experiment draft does not start it, and no page winner is automatically published. Email A/B testing is a separate feature with its own winner rules.

Dashboard → Reports → Email performance shows delivered, opened, clicked, and replied rates per campaign, tracked natively. These are engagement metrics — they answer "did people notice." To answer "did it create business," connect a CRM or Seven16 operating system so outcomes (form submissions, quote requests, opportunities, binds, premium) attribute back to the campaign, audience, and CTA that produced them.

This is an allow-listed private pilot, not a standard self-service feature. The owner pilot has been tested with a real Codex OAuth connection, private draft creation, revocation, and reconnection. Compatibility with every AI client is not implied. 1. If your workspace and client are approved, connect https://app.seven16email.com/api/mcp using Seven16 OAuth. Select the correct workspace. Read access is the default; an authorized writer may separately grant mcp:drafts. 2. Ask the assistant to inspect the workspace and available campaign list/sender choices, then propose a connected campaign using supplied facts. The assistant can propose an email, landing page, and qualification form together. 3. Follow the proposal's Seven16 review link. Review the audience, sender, message, page, form, facts, assumptions, claim findings, and required consent wording. 4. A signed-in human writer chooses Create connected drafts. This creates one private Marketing Studio campaign with linked draft email, page, and form. The assistant itself cannot perform this human-only step. 5. Finish the assets in their editors, activate the form, publish the page intentionally, add the final link to the email, and pass the existing launch checks before any release. The status tool can read the draft receipt. Ordinary proposal acceptance records review only; it does not execute a proposal. Creating connected drafts is an explicit separate operation. No MCP tool sends, publishes, enrolls, approves itself, exports contacts, or changes suppression.

See the full list at /integrations. Current options: - DOT Intel (one click, no keys): pushes carrier/FMCSA data straight into your contacts. - Bring your own data: CSV import, or the signed REST API (/v1) for headless imports. - Sending: your own verified domain, plus one-off transactional sends via the API. You can also connect your own MailerLite account for bulk newsletters — those sends don't count against your plan's allowance. - Outcome sync: your CRM or agency management system can post submissions, quotes, binds and premium to /v1/outcomes so campaigns attribute to revenue. This requires development on your CRM side; there's no turnkey connector yet. - Events out: real-time outbound webhooks for delivery and engagement events. - Texting: connect your own Sendblue account for one-to-one messages from a contact record. Replies and delivery status sync back; STOP is enforced. Bulk texts and automated SMS sequence steps are not available. - AI chats: OAuth MCP for approved private-pilot workspaces; read campaign facts and propose connected drafts for human review. No MCP sending or publishing. - WorkComp Finder: live retail/wholesaler discovery links and a controlled communications integration; general automatic sending is not enabled. See https://seven16email.com/integrations/workcomp-finder. - Coming soon: Zapier. Don't see what you need? The /integrations page has a "Request an integration" link that files a tracked support ticket.

The Developers page includes a typed Node.js 20+ client and copyable recipes at /developers/recipes. The examples use fictional data and cover four common jobs: add a permitted trucking prospect, create a renewal campaign as a draft, post a quote or bind for attribution, and read performance for a production review. The client uses the standard s16_live_ Bearer key, adds your product tenant ID, supplies an Idempotency-Key to every write, and safely reuses that key if a 429 or server error is retried. It never launches when you create a campaign: create returns a draft, and launch is a separate deliberate method after human review. The package source is release-ready in the repository but is not yet published to npm. Until the package name and release are approved, copy the source or use the REST examples and OpenAPI file from /developers. Never paste a real API key into source code, chat, screenshots, or support tickets.

Seven16 Email is the activation layer — other systems push data in and read outcomes back over a signed, HMAC-verified API: - DOT Intel (dotintel.io) can push carrier/insurance leads and DOT data straight into your contacts as a ready-to-target list. One click, no API keys change hands. - Your CRM or agency management system can post outcomes (submissions, quotes, binds, premium) to /v1/outcomes so campaigns attribute to revenue. This needs development on the CRM side — we publish the API, but there is no turnkey connector today. Email tracks engagement natively; connected systems supply the outcome data. That's what turns open/click reporting into revenue reporting.

WorkComp Finder helps people discover workers' compensation relationships and request the appropriate next step. Seven16 Email supplies connected campaign tools: email, landing pages, response forms and surveys, attribution, and reviewed follow-up. Retail agents can find specialist help for difficult workers' comp accounts while preserving their client relationship. Wholesalers, MGAs, and MGUs can present their role and develop retail-agent relationships. Recruiting here means agency and producer relationship development, not a general employment-recruiting service. The connection has two different availability levels. The public retail and wholesaler pages are live and can be linked from reviewed campaigns now. The deeper communications integration has completed a controlled owner test; automatic synchronization and general sending are not broadly enabled. Ask Support to confirm your workspace's approved connection before relying on automation. WorkComp Finder retains authority for its directory, permission, opportunities, and outcomes. Seven16 Email does not turn a public listing, scraped address, inquiry, or click into blanket marketing consent. Connected outcomes must actually be returned before a campaign can claim quotes, binds, or premium. Connection guide: https://seven16email.com/integrations/workcomp-finder Retail agents: https://www.workcompfinder.com/retail-agents Wholesaler partners: https://www.workcompfinder.com/wholesale-partners

For a retail agency: choose a workers' comp audience you are permitted to contact, create a relevant message and response page, and direct accounts needing specialist help to WorkComp Finder's retail-agent path. Retain your client relationship and use the designated secure route for application documents. For a wholesaler, MGA, or MGU: describe your verified role, territory, and appetite; link to the WorkComp Finder wholesaler-partner path; and run a reviewed introduction or recruitment campaign to eligible retail relationships. Use a qualification form or survey to learn what agents need, then assign the next conversation to a producer. Measure response before claiming business results. Email delivery, a page visit, an inquiry, partner verification, appointment, quote, and bind are different stages. Listing or contacting a firm does not establish appointment or binding authority. Only use verified program and carrier facts in campaign copy. The public paths work today. End-to-end automated handoff depends on approved integration access; neither a campaign template nor an AI draft activates it. Start at https://seven16email.com/integrations/workcomp-finder and choose Retail agents or Wholesaler partners.

The Seven16 network is positioned as a High Hazard WC Program Opportunity: helping retail agencies, wholesalers, and MGAs discover opportunities, develop agency relationships, and start relevant workers’ comp conversations. The network includes Seven16 Email (https://seven16email.com), WorkComp Finder (https://www.workcompfinder.com), Seven16 Intel (https://seven16intel.com), DOT Intel (https://dotintel.io), and MapProof (https://mapproof.app). Seven16 Intel provides distribution intelligence. DOT Intel provides trucking and carrier intelligence. WorkComp Finder supports workers’ comp discovery and retail/wholesale relationships. Seven16 Email supports campaigns and follow-up for permission-eligible audiences. MapProof is also a network member; use its dedicated website or Support for verified product-fit guidance. Explore the network and connection guide at https://seven16email.com/integrations/workcomp-finder. Retail agents can start at https://www.workcompfinder.com/retail-agents. Wholesalers and MGAs can explore partner growth and recruiting at https://www.workcompfinder.com/wholesale-partners. This describes a commercial opportunity, not guaranteed coverage or universal automated integration. Account fit depends on verified program appetite. Network membership does not grant marketing permission, an appointment, or quote/bind authority.

Seven16 Intel (seven16intel.com) is the Seven16 Group distribution-intelligence product for commercial insurance. It helps teams identify agencies, producers, carrier appointments, verticals, and market opportunities. Seven16 Email is the activation layer for permitted audiences: it begins the conversation with email and captures structured responses with surveys.

The product formerly called Modeposit is now MapProof. Its canonical customer-facing website is mapproof.app. Older Modeposit names or domains should be treated as legacy references. Contact support@seven16email.com for current MapProof product-fit guidance while its detailed help content is being verified.

The free trial runs 7 days at the full limits of whichever plan you pick — not a cut-down sample. To start it you choose a plan and enter a card. You are charged $0 that day. Billing begins only when the 7 days are up, and cancelling any time before then costs nothing. A countdown banner in the app shows the days remaining and the date your first charge would land. If you cancel during the trial, or your card fails when the trial ends, the workspace becomes read-only: you can still sign in, view everything, and export your data, but sending, importing, launching campaigns, and adding contacts pause. Nothing is deleted, and choosing a plan restores full access immediately. You can change plans or cancel at any point from Settings → Billing, which opens the Stripe billing portal.

Billing is monthly with no long-term contract — you can cancel anytime and keep access through the end of the period you've paid for. Manage everything under Settings → Billing: pick a plan, see days left on your trial, and open the billing portal to update your card, change plans, or cancel. Plans are priced on the size of your book (contacts), not your send volume. Solo is for a single producer working their own book; Starter for a small agency; Growth and Pro for small and growing agencies; Advanced and Agency for wholesalers, MGAs, and multi-brand distribution teams. Higher plans raise your contact and send limits. Your current usage (sends this month, contacts used) is shown on the billing page so you can see where you are against your plan. Verified FastechHR Network businesses receive private pricing instead of a public coupon. Network and affiliate pricing do not stack. Running several brands or a broker network under one roof? Reach out through the support page and we'll verify access and scope sub-accounts and onboarding with you.

FastechHR Network Advantage is a verified-business channel, separate from the public retail trial. - Public retail keeps the 7-day, card-required trial at the full limits of the selected plan. - A verified Network business can receive a 14-day evaluation with up to 500 contacts and 1,000 managed sends. It ends immediately when the first limit is reached: time, contacts, or sends. - After the evaluation, the same six plans are available at private preferred Network pricing. The exact eligible monthly and annual rate is shown in the signed-in billing page only after the business invitation is verified. - Network access is bound to a verified business invitation and sponsor. There is no reusable public 50%-off coupon, and Network pricing does not stack with affiliate pricing. When the evaluation ends, sending and new contact creation pause until a paid entitlement begins. Existing data remains visible and exportable. Use the support page to request verification; do not paste invitation secrets, payment details, or private business documents into chat.

Your data is yours. You can export your contacts and records at any time, including during a read-only trial lockout. Workspaces are isolated from one another (row-level security), secrets are encrypted at rest, and access is role-controlled and audit-logged. See the Privacy Policy and Terms for the full detail.

The AI assistant answers most product and how-to questions instantly — it's available both on the marketing site and inside the app, grounded in this Help Center. When you need a human: 1. File a ticket at the Support page (/support) — it's tracked, so nothing gets lost. 2. Hit a bug? Use the in-app "Report a problem" button — it files a tracked ticket with the page you're on already attached. 3. Prefer email? Reach the team at support@seven16email.com. Include your workspace name and, if it's about a specific send, the campaign name — it saves a round trip. For account-specific actions like changing a plan or payment method, use Settings → Billing so the change happens on your own authenticated account.