Help & how-to

1. Sign up takes 30 seconds.

Visit /signup, enter your name, brokerage, and work email. Click the magic link in your inbox (from submissions@appetitematch.com) - that drops you into /app already signed in.

2. Your account ships with four sample carriers.

So your first triage produces real matches without any setup. You can edit, delete, or replace them at /app/carriers.

3. Run a sample triage.

On /app, click Paste JSON, then Reset to sample (Acme Plumbing TX), then Run triage. You'll see three carriers scored and 2-3 carrier emails drafted in under 20 seconds.

One at a time.

/app/carriers → + New carrier. Each carrier gets a slug (e.g. atlas_specialty), display name, submission email, and one or more appetite rules (NAICS prefixes, allowed/excluded states, lines, revenue band).

In bulk (CSV).

/app/carriers → Import CSV. Header row + one carrier per line. Use semicolons to separate list values (NAICS, states, lines). Existing carriers (matched on slug) get overwritten.

The agent uses what's in the directory.

If a state isn't in states_in(or is in states_out), the carrier won't match - even if their NAICS prefix fits. Same for revenue band and line of business.

Click "Send to carrier" on a draft.

The cover email goes via Amazon SES. If the submission was uploaded as a PDF, the original ACORD is auto-attached on send - no copy-paste. The recipient is whatever you set as submission_email on the carrier row.

Track replies automatically.

When the carrier replies, our inbound webhook records it against the original draft. You'll see a sky-blue ↩ replied badge on the draft, plus the carrier's reply body inline. Promote to Mark bound with a premium amount, or Mark declined, to feed the bind-rate analytics.

Forward inbound submissions to triage automatically.

Configure your AMS or email rule to forward retail-agent emails to triage+yourorgslug@appetitematch.com(set the alias in Settings → Forward-inbox alias). The PDF gets parsed and a triage run starts automatically. (This requires the SES Inbound rule to be wired on our side - talk to us if you need it activated for your alias.)

Invite teammates.

/app/users → Send invite. They get a magic-link email and land in your org as either an admin (can manage carriers, billing, invites) or a CSR (can run triages, send drafts, mark outcomes).

Audit log.

Every state change is recorded - who triaged what, who sent which draft, who promoted an outcome. Visible at /app/audit. Useful for E&O incident reviews and SOC 2 evidence collection.

Trial limits.

50 triaged submissions per month, free, no credit card. Drafts keep working past the limit but you can't create new ones until you upgrade or the period rolls over.

Upgrade.

Click Upgrade on the usage badge → Stripe Checkout. Pro tier is $499/mo, unlimited triages, full team.

Manage subscription.

Settings panel → Manage subscription → opens Stripe's hosted portal: update card, view invoices, download receipts, cancel anytime.

API key.

Settings panel → Show key reveals your bearer token. Use it as Authorization: Bearer <key> on any endpoint. Rotation invalidates the old key immediately and is audit-logged.

Full surface.

See /docsfor the REST reference, or hit /openapi.json on the API host for the raw schema.

"My triage returned 0 matches."

Likely the submission's primary state isn't in any carrier's states_in, or the NAICS prefix doesn't match. Open the carrier card on /app/carriers and confirm the rule covers the submission.

"DocAI returned mostly labels, not field values."

The PDF was probably blank (a template, not a filled submission). Open it in a PDF reader, fill the input fields, save, re-upload.

"My carrier email landed in the prospect's spam."

Outbound is sent from submissions@appetitematch.com with DKIM and DMARC aligned on our domain. If it still lands in spam, ask the carrier to whitelistappetitematch.com. Most carriers do this for any wholesale broker they work with.

"The 'Send' button does nothing."

Check the green/amber pill in the dashboard header. If SES shows stub, the API isn't configured to send real email yet. Email us - usually a 5-min env-var fix.