The daily driver: Chat, Review, Activity, Search
Vocion Team
Four verbs, no overlap: talk to the team, decide what needs you, observe everything it did, find anything. Activity is new — one feed for every check, run, fire, and sync.
22 posts
Four verbs, no overlap: talk to the team, decide what needs you, observe everything it did, find anything. Activity is new — one feed for every check, run, fire, and sync.
Missions are now charters a team owns continuously — checked on a schedule, discharged with only the work that's needed. Plus schedule triggers for workflows, agent steps, and an Automation page for every clock in your deployment.
Mission checks now remember what they flagged (threads age across checks), high-confidence proposals can execute on enabled trust rules, workflows can ask a human for input mid-run, and briefings publish to their own page.
Agents are who. Missions are goals. Workflows are procedures. Automations — new and first-class — are when. Plus: watch your agents actually think, with streamed chain-of-thought.
Restrict any source to specific members — enforced in chat and search as an intersection, never a leak. Plus e2e:demo — the full briefing + CRM sweep as an executable test, passing 9/9 against live production data.
Agents now sweep the last 48 hours of email, detect what moved a deal forward or backward, and queue scored CRM updates for one-click human approval — the full loop, running on live HubSpot + Gmail data.
Vocion deployments are multi-user from day one — a Members page to see everyone, manage roles, and mint one-time invite links that need zero email infrastructure.
Credential onboarding lands — paste a token or run one Google OAuth consent and your connectors sync for real. And agents gain propose_action: CRM updates and emails proposed with confidence scores, gated behind your review queue.
The dashboard brand is now a slot — set a wordmark, a subhead, and your own glyph via build-time env, so a Vocion deployment wears your identity and the OSS build carries no one else's art.
Pending work now routes to a specific person — per-person queues, an unassigned triage lane, and snooze — so a workspace with many humans can actually divide the approvals.
The second action on the framework — update a deal's stage, a contact's fields, a missing next-step — proposed by an agent, approved by a human, executed against the CRM.
The trigger runner. An inbound event — a prospect reply, a meeting ending, a deal changing stage — fans out to the workflows subscribed to it, deduped and audited. The last load-bearing piece of the loop.
Agents now carry a role, a work mode, and a team — so a deployment reads as an org chart: one Lead you brief, its specialists doing focused work. A new Teams view makes it visible.
The write half of the runtime. A narrow, typed action (send an email, update a record) that an agent proposes and a human approves — the same permission model as everything else, now applied to mutation.
The control plane gets its first write surface — the unified review queue, list and decide, on tenant Bearer tokens that resolve into the same permission model as a human.
A source's schedule now actually fires — runSync runs inside a durable Temporal Workflow on a Schedule, so connectors keep their knowledge fresh on their own cadence, crash-safe and incremental.
A few days ago we wrote about the platform direction FirstHQ was forcing. Here's the first wave, shipped: client/team-scoped retrieval with document ACLs, a discovery-vs-mutation permission model with one review queue, and durable, resumable, incremental ingestion.
The agent/tool plane goes multi-tenant. A single Streamable-HTTP MCP endpoint where the org is derived from a tenant Bearer token — every tool call scoped to that org, under the same permission model as a human.
We're building FirstHQ (an AI team HQ for agencies) on Vocion — and using it as a forcing function for the platform. Here's the architecture direction it's driving: scoped retrieval with document ACLs, durable ingestion pipelines, a discovery-vs-mutation permission model, and a clean split between the MCP tool plane and the API control plane.
The Drive connector — Docs, Sheets, Slides, and text files exported into scoped, retrievable knowledge — completes the connector set the two reference deployments run on.
Two more waves of platform work shipped: tenant API tokens that resolve into the permission model (the control plane), and a connector pack — Google Ads, GA4, HubSpot, Gmail, Slack — on the durable, incremental ingestion pipeline.
The credential vault is now wired into the ingestion pipeline — a connector's OAuth/API credentials are stored encrypted-at-rest per tenant and resolved at sync time, so the connector pack can actually authenticate.