Inbound signals
Inbound is the first phase of Field's pipeline. Every signal that arrives — email, uptime alert, portal request, scan finding, time proposal — enters here before being triaged into work.
Signal types
Inbound organizes signals by source. Each source appears as a tab:
Gmail emails auto-triaged into the queue. Each email gets an AI-generated Signal summary (if AI is configured) or a deterministic assessment with keyword flags, client match, and read time.
Proposals
Time entry proposals from Harvest, API, or Field Agent. These are pre-attributed work items that need operator approval before entering the billing record.
Uptime
Downtime and recovery alerts from Field's built-in monitoring or Better Uptime integration. Auto-matched to sites by URL.
Portal
Requests submitted by clients through the portal.
Scans
Findings from automated site scans — new issues, resolved issues, score changes.
Read / unread
Items arrive as unread (solid dot indicator, bold title). Expanding an item marks it as read. Use “Archive reviewed” to clear items you've seen and decided don't need action.
Triage
The Triage button on each item moves it into the Work pipeline. For matched items, it assigns directly. For unmatched items, a selector lets you pick the client and site. Field pre-populates the work type and priority from subject line keywords when possible.
Without AI
If no operator AI key is configured, emails still arrive with a deterministic Signal — keyword flags ([urgent], [request], [billing]), client match status, thread count, and estimated read time. The Cmd-K command bar shows quick filters instead of natural language. Everything works — AI enhances but isn't required.
Next: Work queue →