ENRICH Branded Messaging lets businesses send interactive, verified text messages that show your brand name and logo, engage customers with rich content, and support two-way conversations using RCS technology.

Pre-requisites

• Access - Your ENRICH login. You can reach ENRICH through the customer portal or by going directly
  to enrich.firstorion.com — either way you sign in with your First Orion credentials (there's no separate
  ENRICH account to create).
  • If you manage messaging on behalf of other businesses (a reseller account), you'll pick the business you're working in from a switcher at the top of the portal before doing anything else. If you only manage your own business, you can skip that — you're always scoped to your own account.
• Business / brand verification details (used for vetting)
  • Legal business name, Full company address, EIN (employer ID) in 12-3456789 format, Brand industry (e.g. Retail, Healthcare, Financial), Estimated monthly message volume, A verification contact: name, title, business email, and company website.
• Your agent's public identity (what recipients see)
  • Display name (max 40 characters)
  • Short description (max 100 characters)
  • Logo — JPEG, exactly 224 × 224 px, max 50 KB
  • Banner — JPEG, exactly 1440 × 448 px, max 200 KB
  • An accent color as a 6-digit hex code (must be readable on white — at least 4.5:1 contrast)
  • Contact methods recipients can tap: up to 3 phone numbers, 3 emails, and 3 websites (each needs a short label like "Support" or "Sales"). At least one phone or email is required.
  • Links to your privacy policy and terms of service (both must be HTTPS)
• How the agent behaves - Use case: Promotional, Transactional, OTP (one-time passcodes), or Multi-use. Plain-language descriptions (each max 100 chars) of: what interactions look like, what triggers a message, how people opt in, and how people opt out. At least one test phone number (US, E.164 format like +15554443333 ) — up to 20. A webhook URL if you want delivery/reply events pushed to your systems (Optional).
• If you plan to connect HubSpot - Admin access to your HubSpot account (you'll approve an app install). A HubSpot plan that supports custom event reporting. Professional or Enterprise if you want to use the data in reports, lists, and workflows (see the HubSpot section)

The Big Picture

flowchart LR
    A["1. Log in\n(portal)"] --> B["2. Create your agent\n(4-step wizard)"]
    B --> C["3. Agent goes through\nverification & launch"]
    C --> D["Active"]

    style A fill:#003da6,stroke:#2C5F8A,color:#fff,rx:10
    style B fill:#003da6,stroke:#3A7A3A,color:#fff,rx:10
    style C fill:#003da6,stroke:#B07A20,color:#fff,rx:10
    style D fill:#003da6,stroke:#1A9B50,color:#fff,rx:10

Once your agent is up, there are two optional things you can do at any time — in either order, and
neither is required to send messages:

• Connect HubSpot — so your ENRICH messaging activity shows up in your CRM.
• Generate API keys — for programmatic / integration use.

Step 1 - Login to the ENRICH Portal

1. Open ENRICH through the customer portal, or go directly to enrich.firstorion.com, and sign in with
   your First Orion credentials.
2. Resellers only: use the business switcher at the top of the page to select the business you're
   setting up. Everything you do next applies to that business. (If you only manage your own business,
   skip this — you're always scoped to your own account.)
3. You'll land on the Overview home screen. If you have no agents yet, this is where you'll start one. If
   you already have agents, you'll see them listed here along with performance metrics (messages
   sent/received, rich media count, opt-out rate) that you can filter by agent and by Today / This Week
   / This Month.

Step 2 - Create your Agent

From the Overview screen, start a new agent. The portal walks you through a 4-step wizard with a progress bar. Your work is saved as a draft as you go, so you can leave and come back.

2.1 Agent Details (Your Agents Public Identity)

This is everything recipients see. You'll provide:

• At least one phone number or one email is required so recipients have a way to reach you.

2.2 - Verification (who the Brand is)

Used to verify the brand with carriers. You'll provide:

• Verification contact: name, title, business email, company website
• Legal business name and full company address
• EIN ( 12-3456789 format)
• Brand industry (dropdown)
• Estimated monthly message volume (dropdown: up to 10K / 10K–100K / 100K–1M / 1M+)

2.3 Experience (how the agent behaves)

• Use case: Promotional, Transactional, OTP, or Multi-use
• Interactions description — what a conversation with your agent looks like
• Message trigger description — what causes a message to be sent
• Opt-in method — how recipients consent to receive messages
• Opt-out method — how recipients stop messages
• Test numbers — at least one US number in E.164 format (up to 20). These are the numbers allowed to receive messages while the agent is in testing.
• Webhook URL (optional) — an HTTPS endpoint where ENRICH can push events

2.4 Summary (review & submit)

Review everything on one screen. You can jump back to any step to fix something. When it looks right,
submit to create the agent.

Step 3 - What happens after you submit

Your agent moves through a series of statuses as it gets verified and launched across carriers. You'll
see these on the agent's status badge:

• Use the In Test phase to send a test RCS message to your test numbers and confirm the branding,
  contact buttons, and message flow look right before going fully live.

After your agent is live - Optional Add-ons

Everything below is optional and can be done at any time once your agent exists, in either order.

Connect HubSpot

Connecting HubSpot lets your ENRICH messaging activity show up inside your CRM, so your team can
see and report on it alongside everything else they track about a contact.

What the integration actually does

• ENRICH sends app events into HubSpot — structured records of messaging activity (for example, a message with a delivery status, or a reply) that land on the associated contact's timeline. You then surface and analyze that data using HubSpot's custom reporting. The data is sent into HubSpot as app events; it isn't a native HubSpot object, so reporting is done through HubSpot's custom report builder, lists, and workflows rather than out-of-the-box standard reports.
• By design, no message content is stored in HubSpot — only structured fields (message type, status, reply type, identifiers, failure reason, etc.). This keeps message bodies and personal content out of your CRM.

HubSpot plan requirement

• Receiving the events on a contact timeline works on any HubSpot tier.
• Using that data in reports, lists, lead scoring, and workflows requires a Professional or Enterprise subscription (any HubSpot hub). Free and Starter portals can see the timeline entries but can't build reporting or segmentation on them.

Note: entitlement for a Marketplace app's timeline data can differ slightly from a portal's own custom events, so confirm the exact plan requirement before relying on reporting if it's business-critical.

How to connect

1. In the ENRICH portal, find the HubSpot connection option (on the Overview / home area). (Confirm the exact button label and placement in the live portal — the connect action opens HubSpot's install flow in a new tab.)
2. Click to connect. A new browser tab opens HubSpot's app install / authorization screen.
3. Sign in to HubSpot if prompted, choose the correct HubSpot account, and approve the requested permissions. (You need HubSpot admin rights to approve an app install.)
4. After approving, you're returned to the flow. Back in the ENRICH portal, the HubSpot connection shows as connected.
5. From there the portal gives you a Manage action (opens your HubSpot account) and a Disconnect action if you ever need to turn the integration off.

Verify it's working

• In HubSpot, open a contact who has had ENRICH messaging activity and check their timeline for ENRICH events.
• To report on activity, build a custom report (or list/workflow) in HubSpot using the ENRICH event data — this is where delivery rates, reply triggers, and similar insights come from.

Disconnecting

Use Disconnect in the ENRICH portal to deactivate the integration. Events stop flowing to HubSpot; historical timeline entries already in HubSpot remain (app-event occurrences can't be retroactively deleted).

Generate API Keys

If you're integrating ENRICH with your own systems programmatically, create API credentials from the
API Keys page.

1. Go to API Keys and click Generate Key.
2. Give the key a descriptive name (e.g. "Production Server") so you can identify it later.
3. ENRICH generates an API Key and a Secret Key.
   1. NOTICE! The Secret Key is shown only once - copy and store it securely immediately. The API Key can be viewed again later; the secret cannot.

4. Store both in a secure place (environment variables / a secrets manager — never in source code or
   shared files).

Managing keys - You can disable a key to immediately cut off access for anything using it, and enable it again later. Rotate keys periodically and disable any unused keys. Reference docs and service status are linked from the API Keys page (developer.firstorion.com and status.firstorion.com).

Quick setup checklist

• Logged in to the ENRICH portal
• (Resellers only) Selected the right business from the switcher
• Gathered brand verification details (legal name, address, EIN, industry, volume, verification contact)
• Prepared agent identity assets (logo 224×224, banner 1440×448, accent color, name, description, contact methods, privacy + terms URLs)
• Defined agent behavior (use case, interactions, trigger, opt-in, opt-out, test numbers)
• Created the agent and submitted it
• Tested with test numbers while In Test
• Agent reached Active
• (Optional) Connected HubSpot and verified events on a contact timeline
• (Optional) Generated and securely stored API keys

Notes & things to confirm against the live product

• HubSpot connect button label/placement — confirm the exact wording and where it sits in the current portal UI before publishing to customers.
• Field limits and image specs above are taken from the current portal validation rules and should hold, but it's worth a final pass against the live form before this goes to customers.