Port 5100 inbox routing

Email-Agent Automation & Multi-Inbox Routing

Unify business inboxes on port 5100 — OutreachEngine campaign replies in crm_reply views, website leads in formspree_lead, manual threads separate, with KL / KG / ST brand maps and bounce signals back to the CRM scheduler.

5100 Email-Agent service port

3 Intent views — crm_reply / formspree_lead / manual

KL·KG·ST Brand-mapped inboxes — Gmail, Zoho, Microsoft

Book a Consultation CRM Outreach Lane

Three queues — not one buried Gmail search

Email-Agent is the inbox lane inside Knight Command. Outreach sends from OutreachEngine; replies land in crm_reply. Website forms route to formspree_lead. Owner conversations stay in manual views. Brand maps keep Knight Logics, Knight Group, and Screen Team credentials isolated — bounce feedback loops to OutreachEngine before the next capped send window.

Lane 1 — crm_reply

OutreachEngine replies surface in a dedicated CRM view

When a prospect answers a first_touch or followup send, Email-Agent classifies the thread as crm_reply — not mixed with newsletters, Formspree intake, or personal mail. Operators triage campaign responses daily without hunting Gmail labels.

Reply detection Inbound mail matched to OutreachEngine send logs — list, variant, and brand lane visible before you draft a response.
CRM Sent folder Outbound campaign mail stays in CRM Sent — separate from manual owner threads and form-lead acknowledgements.
Speed options Push notifications or after-hours auto-acknowledge while the lead is still comparing vendors. CRM outreach page →

Autoplaying muted — use controls to unmute

Lane 2 — formspree_lead

Website form fills land in Form Leads — not campaign noise

Formspree webhooks and site contact forms route into formspree_lead views per brand. Estimate requests, consult forms, and referral landing pages stay isolated from OutreachEngine traffic so intake does not get buried under CRM replies.

Webhook + IMAP intake Form submissions create structured queue entries — not a forward-to-personal-Gmail chain nobody monitors.
Brand-mapped routing KL, KG, and ST each get the right company mailbox — Screen Team form leads never appear in Knight Group views.
Optional auto-acknowledge After-hours acknowledgement templates scoped per brand — not one generic “we got your message” for every lane.

Lane 3 — Manual threads

Owner conversations stay operator-owned

Not every email is a campaign reply or a form lead. Manual Sent and manual inbox views keep day-to-day sales conversations, vendor threads, and one-off customer mail out of crm_reply and formspree_lead queues — so morning triage stays fast.

Folder discipline Inbox, Form Leads, CRM Replies, CRM Sent, and Manual Sent mirror how your office actually works — not one undifferentiated stream.
Thread tagging Lead-source attribution when a manual thread started from outreach or a form — without merging queues.
Morning review runbook Unread crm_reply count first, then formspree_lead intake, then manual owner threads — documented for every operator.

Email-Agent routing dashboard — crm_reply, formspree_lead, and manual folder separation

Lane 4 — Brand maps

KL / KG / ST credentials and templates stay isolated

Multi-brand Tampa Bay operators cannot afford cross-lane reply mixups. Email-Agent maps Knight Logics, Knight Group, and Screen Team to separate provider credentials — Gmail, Zoho, or Microsoft — with templates and senders that never cross accounts.

Per-lane credentials Each brand connects its own inbox — KG replies do not appear in KL or ST mapped views by accident.
Provider flexibility Gmail, Zoho, and Microsoft supported — wire the accounts your team already uses instead of forcing one provider.
Faith Works lane faithworks maps available where a fourth brand lane is active — same isolation pattern as kl / kg / st.

Lane 5 — Bounce feedback

Bounce signals loop back to OutreachEngine list hygiene

Bad addresses poison domain reputation when they keep receiving capped sends. Email-Agent surfaces bounces and delivery failures to operators and feeds suppression back into OutreachEngine — so the next first_touch window does not hit addresses that already failed.

Operator alerts Failure notifications when a thread or webhook breaks — not silent drops in a shared inbox.
CRM pairing OutreachEngine send logs tie replies and bounces back to list and message variant. CRM outreach case study →
Audit trail Campaign logging connects triage decisions to the outreach lane that started the conversation.

OutreachEngine CRM queue — partner send lane paired with Email-Agent reply routing

Lane 6 — Knight Command embed

Port 5100 inside the operator shell — or direct

Email-Agent embeds in the Knight Command Email Agent tab beside Outreach CRM, Referrals, and Social Poster. Port 5100 is also reachable directly for operators who need a standalone inbox window — same routing rules either way.

Single-sign-on workflow Morning review opens Knight Command once — CRM queue depth, email backlog, and social last-success in one login.
Mobile-readable triage Reply layout works on phone for urgent crm_reply responses while crews are in the field.
Shell context See Knight Command case study → for full /admin architecture.

Knight Command ops shell with Email Agent tab embed on port 5100

What this includes

Multi-inbox routing deliverables — brand maps, view types, provider wiring, and operator runbooks.

CRM

crm_reply detection

Outreach replies land in dedicated CRM views for follow-up queues — paired with OutreachEngine send logs.

Explore CRM outreach

Leads

formspree_lead views

Website form leads separated from campaign and personal traffic — webhook and IMAP intake.

Explore workflow triggers

Unify

Multi-inbox routing

Business accounts unified with folder rules on port 5100 — Gmail, Zoho, or Microsoft per brand.

Brands

KL / KG / ST mapping

Knight Logics, Knight Group, and Screen Team lanes stay isolated — templates and credentials never cross.

Alerts

Urgent reply surfacing

Push notify or auto-acknowledge when a high-fit lead replies — without living in email all day.

Hygiene

Bounce suppression loop

Delivery failures feed back to OutreachEngine before the next capped send window fires.

Inbox routing — production UI captures

Verified Email-Agent screens from port 5100 — folder separation, brand maps, and CRM reply discipline. Not a generic “AI inbox” mockup.

Multi-inbox Brand-mapped folders

crm_reply, formspree_lead, and manual views in one operator UI

Morning review opens Email-Agent first: unread crm_reply count, then formspree_lead intake, then manual owner threads. Folders match the work — not one undifferentiated Gmail search across every brand you operate.

CRM Sent separate from Manual Sent and Form Leads
Per-brand credential maps for KL, KG, and ST
Embeds in Knight Command Email Agent tab

Email-Agent routing dashboard showing provider-to-view bounce loop and form vs crm_reply separation

Provider → view Bounce loop

Form intake and CRM replies never share the same queue

Formspree webhooks and IMAP inboxes fan into structured queues before anyone opens Outlook. Bounce and failure signals notify operators and suppress bad addresses in OutreachEngine — protecting domain reputation across daily send caps.

Webhook + IMAP triggers into structured queues
Auto-acknowledge scoped per brand lane
Failures surface in logs — not silent inbox drops

Operator UI Brand switcher and inbox routing on port 5100.

Knight Command Email Agent embed beside CRM and social tabs — **Knight Command** Email tab beside outreach, referrals, and social ops.

OutreachEngine CRM queue — send lane paired with Email-Agent crm_reply routing — **Reply loop** Outreach sends → Email-Agent crm_reply triage (partner lane only).

How we build it

A clear path from inbox inventory to daily operator runbook — scoped to brands and providers you already use.

Inbox inventory

List accounts, brands, and who sends outreach from each — map KL, KG, ST, and any faithworks lane before wiring credentials.

View rules

Configure crm_reply, formspree_lead, and manual conversation paths — folder names that match how your office triages mail.

Provider wiring

Connect Gmail, Zoho, or Microsoft inboxes with per-brand credential maps and webhook intake for Formspree forms.

Embed & auth

Deploy on port 5100 with Knight Command Email Agent tab embed — mobile-readable triage layout for urgent replies.

Bounce feedback & runbook

Loop bounce signals to OutreachEngine list hygiene — document morning review order for every operator.

Outcomes we design for

Business email ops outcomes when CRM replies and form leads stop living in personal Gmail.

Reply discipline

Outreach responses reviewed daily from dedicated crm_reply views — not buried in a personal inbox until tomorrow.

Brand separation

KG replies do not appear in KL or ST mapped views by accident — templates and senders stay lane-isolated.

Faster follow-up

Operators see unread crm_reply count without searching Gmail labels — speed wins estimate-first trades.

Form lead clarity

Website intake in formspree_lead — separate from campaign noise and manual owner threads.

List hygiene

Bounce suppression before the next OutreachEngine send window — domain reputation protected across brands.

Audit trail

Campaign logging ties replies back to list and message variant — triage decisions are defensible.

Related proof & examples

Email-Agent proof via the OutreachEngine reply loop and Knight Command embed — inbox routing, not vague automation claims.

OutreachEngine CRM production queue paired with Email-Agent reply routing

Live workflow

OutreachEngine send + reply loop

Flask SQLite CRM with kl, kg, st brand lanes — scheduler cadence and Email-Agent crm_reply routing on live client campaigns.

Internal system

Knight Command ops shell

Unified /admin tabs for CRM, email, social, referrals, and logs — Email-Agent on port 5100 embedded beside outreach.

Knight Command admin command center — workflow hub connecting email lane

Connective tissue

Workflow automation hub

How CRM, Email-Agent, social, and dispatch lanes connect through Knight Command — link-out page for cross-lane ops.

Email-Agent inbox routing in the full growth stack

Full stack

Business growth systems

Email-Agent as Lane 2 in the connected growth stack — website, outreach, inbox, social, referrals, and dispatch phased in.

Common questions

How do crm_reply and formspree_lead views differ?

crm_reply is for OutreachEngine campaign responses — replies to first_touch and followup sends. formspree_lead isolates website form intake from campaign and personal traffic. Manual threads stay in separate views so operators never hunt one mixed Gmail inbox.

Which email providers work?

Gmail, Zoho, and Microsoft are supported with per-brand credential mapping for KL, KG, ST, and faithworks lanes where active. Wire the accounts your team already uses — no forced provider swap.

Is Email-Agent only for CRM replies?

No — it also routes Formspree and manual business threads. CRM reply management is one view among several. Website leads and owner conversations get their own queues.

How does bounce handling work?

Bounce and failure signals notify operators and feed back into OutreachEngine so bad addresses stop before the next send window. List hygiene is part of the inbox lane — not a separate spreadsheet task.

How is this different from service-ai-automation?

Business automation covers all production lanes — Knight Command, CRM, email, social, referrals, and dispatch. This page is the dedicated inbox-routing depth: port 5100, view types, brand maps, and bounce loops. AI business automation covers assistive drafts on top of these deterministic rules.

Can I access Email-Agent outside Knight Command?

Port 5100 is reachable directly; Knight Command embeds it for single-sign-on operator workflow. Same routing rules either way.

Who is this for?

Multi-brand Tampa Bay operators drowning in mixed inboxes — especially teams already running OutreachEngine who lose campaign replies in personal Gmail.

Scoped as inbox lane, CRM pairing, or full growth-system embed. See pricing or book a consult for a written estimate.

Business Automation CRM Outreach Workflow Automation CRM Case Study Knight Command Pricing

Inbox slowing outreach?

Tell us which brands, providers, and form paths you run — we will map crm_reply, formspree_lead, and manual routing rules for Email-Agent on port 5100.

Book a Free Consultation