Changelog

Operators told us they were managing campaigns from a laptop because the dashboard was not usable on a phone. This release fixes that. Every surface now adapts to small screens with a slide-in sidebar drawer, and the email backbone gained a 3-tier sending hierarchy.

• Mobile dashboard across home, conversations, CRM, opportunities, calendar, campaigns, call logs, contacts, and settings
• Sidebar drawer with a hamburger menu replaces the fixed desktop rail on phones and tablets
• 3-tier email routing resolves a sending domain in order: organization, then agency, then platform default

The platform has had a v1 API since March. This release gives it a proper home at api.strideops.ai, with an interactive reference that stays in sync with the code because it is generated from the same schemas the API validates against.

• OpenAPI 3.1 spec generated from our Zod schemas and served at /api/v1/openapi
• Interactive reference with per-endpoint pages, request builders, and copyable examples
• AI assistant trained on the docs answers integration questions inline
• Brand-aware docs that re-skin for white-label agencies on their own domains

# The spec is live and machine-readable
curl https://api.strideops.ai/api/v1/openapi

CRM sync used to be a single outbound pipe that was hard to reason about when something went missing. We replaced it with a router that models each direction independently, ships every event to a log you can filter, and rolled out behind a shadow read before going live.

• Per-direction model so inbound and outbound sync are configured and tracked separately
• Live router with a shadow phase first, so we validated parity before cutting over from the legacy path
• Integration logs with stat tiles that double as one-click filters for retries and failures
• Mapping watermarks to resume incremental pulls instead of re-scanning every contact

Two things were slowing agencies down: collecting SMS opt-ins in a compliant way, and connecting Google Calendar under their own brand. Both are handled now, and the telephony layer stopped caring which carrier sits underneath.

• SMS opt-in landing pages with A2P-ready consent language and a privacy policy that syncs the lead straight into CRM
• White-label Google OAuth so the calendar connect screen carries the agency brand, not ours
• Signed OAuth state to harden the connect flow against tampering
• Unified provider credentials that resolve Twilio, Telnyx, and Vonage through one path

You can now click a LIVE badge and watch a call as it happens, with the transcript streaming in and a duration counter ticking. Behind it, the voice runtime moved to Pipecat 1.0 and inbound callbacks now stitch themselves back to the campaign that triggered them.

• Live listen-in streams call audio to the dashboard over a WebSocket relay
• Live transcript and duration counter inside the call detail view
• Inbound callback attribution detects when a missed-call lead rings back and re-attributes it to the originating campaign
• Agent continuity routes that callback to the same agent the contact spoke with

Scheduling across timezones is where booking tools quietly break. We threaded timezone resolution through availability, booking, and confirmation so a 2pm slot means 2pm for the contact, the host, and the calendar invite. HubSpot also started receiving call outcomes automatically.

• End-to-end timezones for availability, booking, dashboards, and invite rendering
• Parallel availability requests so multi-host calendars resolve faster
• HubSpot call logging with status mapping, plus appointment sync into the timeline
• Meeting capture through Recall and Fireflies for recorded calls

Automation used to mean asking us to wire something up. Now you drag nodes onto a canvas. Workflows fire on real events from across the platform, branch on conditions, call out to other systems, and can hand a step to an AI agent.

• Visual builder in the style of n8n, with a node canvas and live execution overlay
• Trigger.dev engine running the automations underneath
• Event triggers for forms, appointments, contacts, and tag changes
• Power nodes for inline code, HTTP requests, and AI agent steps

This is the release that turned single agents into running campaigns. Load a list, pick your agents, and dial from a pool of local numbers so contacts see a familiar area code. Every call resolves to a disposition, and those dispositions drive what happens next.

• Voice and SMS campaigns from a single contact list with drip scheduling
• Phone number pool distribution with local presence dialing per contact
• Multi-agent selection to spread volume across several agents
• Disposition system separating fixed system outcomes from AI-classified ones

Everything you can do in the dashboard, you can now do over HTTP. The v1 API exposes agents, calls, phone numbers, tools, and knowledge bases, secured with managed API keys. Alongside it, two-way CRM sync landed for the systems agencies actually use.

• v1 REST API for agents, calls, phone numbers, tools, and knowledge bases
• Outbound call API to launch a call programmatically and receive results by webhook
• HubSpot and GoHighLevel integrations with cross-sync of contacts and activity
• API key management with encrypted keys you can reveal once and revoke anytime

curl -X POST https://api.strideops.ai/api/v1/calls \
  -H "Authorization: Bearer $STRIDE_API_KEY" \
  -d '{ "agentId": "agt_123", "to": "+15551234567" }'

Agencies resell StrideOps under their own brand, so the brand has to be theirs from the first pixel. This release resolves branding on the server before the login page renders, moves custom domains onto Cloudflare for SaaS, and adds the billing pieces an agency needs to run sub-accounts.

• Agency white-label domains provisioned through Cloudflare for SaaS
• Server-side branding resolution so a white-label login shows the right logo and colors with no flash
• Cinematic login design system for branded sign-in screens
• Invite codes to gate registration and onboard sub-accounts cleanly

A voice agent that can book is only as good as the calendar behind it. This release connects the three calendars businesses actually run on, adds team pools so a booking can round-robin across people, and keeps everything in sync both ways.

• Google, Outlook, and Microsoft 365 calendar integration with proper OAuth and admin consent
• Calendar pools that distribute bookings across team members with per-member overrides
• Bi-directional sync so external busy time blocks availability and new bookings push out as events
• ICS invites emailed to attendees, including an Outlook-compatible path

The whole month went into making the agents feel fast and making calls easy to inspect afterward. We instrumented every turn, tuned voice activity detection, and rebuilt the call log so you can see exactly where each millisecond went. Median voice latency now sits at 427ms.

• 427ms median latency through voice-activity-detection tuning and turn-tracking observers
• VAPI-style call logs with per-stage timing metrics in the call detail panel
• Multi-provider telephony across Twilio, Telnyx, and Vonage from one interface
• End-of-call reports with structured data extracted from the conversation

Three of the six products grew up this month. The content studio became a real workspace for organizing generated assets, the knowledge base got retrieval settings and tracing, and a set of discover integrations started pulling outside data into the platform.

• Content studio with folders, drag-and-drop, custom categories, and an avatar library
• Knowledge base with configurable RAG settings and chat tracing for observability
• Universal documentation scraper with deep crawling to build a knowledge source from any docs site
• Discover integrations for deep research jobs, Facebook Ads, Apify scrapers, and Google Drive