Novedades

Lead management and campaign work gained a more connected operating surface.

• Refined CRM workspace views for reviewing customer context, lead progress, ownership, and the next action.
• Expanded campaign-oriented email work so approved templates, customer segments, and follow-up could remain connected to the record.
• Improved the path from a campaign response into qualification, booking, task ownership, and reporting.

Social work became easier to plan, monitor, and connect with the wider customer workflow.

• Expanded the foundation for publishing, scheduled social activity, and performance review across supported connected channels.
• Added clearer listening and response workflows so relevant signals could be reviewed with a defined owner and next action.
• Kept social operations close to campaign, customer, and reporting context instead of isolating them in another tool.

More dependable scheduling from availability through the meeting and follow-up.

• Improved calendar availability, invitation, connected-provider, and meeting-readiness behaviour for supported booking workflows.
• Kept guest, appointment, CRM, and automation context connected as a meeting moved from scheduling through completion.
• Strengthened the operational controls that help teams manage changes, cancellations, and the next customer step.

Search evidence broadened from technical findings into more practical visibility research.

• Expanded the SEO workspace with connected research for search performance, authority, competitors, and AI-surface visibility.
• Made the evidence easier to connect with a priority, owner, and reporting narrative rather than leaving it as a disconnected audit finding.
• Improved the path from a crawl or search signal to a repeatable next action for the team or client.

A faster, more dependable way to explore Spacebrain.

• Strengthened public-site delivery and navigation across the product catalogue.
• Improved the shared visual system and accessibility treatment across key public pages.
• Added resilience work around localized journeys and the free SEO audit experience.

More reusable starting points for customer journeys and shared work.

• Expanded professional starting templates and reusable journey structures in supported builders.
• Improved localization for supported customer-facing experiences and languages.
• Extended lifecycle automation, collaboration, and performance work across affected product surfaces.

Searchable, practical guidance for operating Spacebrain.

• Launched public documentation with role-based onboarding, operating guides, and troubleshooting.
• Made product guidance easier to search, link to, and read in AI-friendly Markdown.
• Published the original historical changelog that this public timeline now carries forward.

Projects gained richer views, ownership, dependencies, and recurring work.

• Added sections, workflow columns, fields, labels, filters, and saved views for shared planning.
• Expanded Kanban, Calendar, and Timeline views for flow, schedule, overlap, and milestone planning.
• Added richer task context, dependencies, milestones, and recurring-work support where available.

Deeper crawl evidence and more repeatable SEO reporting.

• Expanded the bounded Site Audit into deeper inventories for supported pages, links, and images.
• Connected technical findings with crawl coverage, page evidence, and incomplete-snapshot warnings.
• Broadened connected research and reporting for visibility, rankings, keywords, competitors, and authority.

More complete multi-step customer journeys, from quiz to conversion.

• Expanded multi-step funnel building with templates, quick starts, generated proposals, and blank flows.
• Added supported commerce patterns and native quiz journeys for question-led visitor flows.
• Improved launch-readiness checks and customer-facing Chat Widget configuration.

Search evidence, lead capture, lifecycle messaging, and task ownership move closer together.

• Extended SEO from technical audit work into connected search evidence, research, authority, and reporting.
• Added quiz-oriented Funnel starting paths and Webinar lifecycle messaging around registration through replay.
• Made landing-page outcomes easier to route into shared task operations.

Choose a useful next step before setting up everything.

• Added outcome-led onboarding and clearer paths to the first useful workflow.
• Strengthened monitoring, accessibility, and design guardrails for the public product experience.
• Improved the foundation for a more reliable first Spacebrain interaction.

Turn a domain into a practical SEO starting point.

• Made the audit journey reusable and locale-aware from a first domain check through to the report.
• Improved report guidance so teams can turn findings into an informed next action.
• Expanded multilingual conversion support around the public audit experience.

Build, publish, measure, and improve focused campaign destinations.

• Introduced a focused Landing Pages builder with draft autosave and explicit publishing.
• Added lead review and supported traffic, conversion, goal, and call-to-action evidence.
• Added controlled experiment tools for comparing intentional page variations where available.

A safer, guided way for agencies to request customer-authorized access.

• Expanded guided provider and asset access requests for agency client connections.
• Added supported Google Ads access requests alongside eligible workspace assets.
• Kept the handoff client-authorized rather than asking agencies to collect reusable credentials.

Ask for honest reviews and, where enabled, manage Google review operations.

• Introduced neutral review-request destinations through eligible channels.
• Added link-only mode for merchant-supplied public review URLs without synchronization.
• Enabled supported Google Business Profile review monitoring and deliberate owner replies where approved.

Safer form revision, richer questions, and more ways to share.

• Expanded eligible Forms with presentation controls, version history, and recovery-oriented editing.
• Added file-upload questions within configured limits.
• Added compact public sharing while preserving the draft-first, explicit-publish model.

More operating surfaces for automation, assisted calling, collection, and website conversation.

• Expanded multi-step Workflow building with supported triggers, conditions, actions, and executions.
• Added Power Dialer for working through approved calling lists with contact context and outcomes.
• Added dedicated Forms and customer-facing Chat Widget building experiences.

Bounded site auditing plus more control when creating customer-facing work.

• Added a bounded Spacebrain crawl that can inspect a site without a paid third-party request.
• Made technical findings easier to review alongside crawled page evidence.
• Expanded editing choices across supported content builders while retaining draft-first review.

Broader search evidence, messaging-compliance preparation, and secure client access requests.

• Expanded SEO intelligence across crawling, search evidence, rank review, research, authority, AI visibility, and reporting.
• Added SMS Trust Center for preparing and tracking supported compliance or carrier-registration work.
• Added structured agency-to-client connection requests and authorization-progress tracking.

More confident launches and richer attendee journeys.

• Added pre-launch Webinar readiness checks for required configuration and provider lifecycle checks.
• Expanded confirmation, waiting-room, live, replay, and ended attendee experiences.
• Improved Funnel starting points, readiness checks, preview, publishing lifecycle, and step-level evidence.

A simpler security option for eligible users and stronger abuse prevention.

• Added passkey management through account security settings on supported devices and browsers.
• Strengthened public sign-up and sign-in paths against automated abuse.
• Clarified the relationship between passkeys, password recovery, and other account-access paths.

A shared place to assign, schedule, and complete operational work.

• Introduced personal and team task workspaces with projects and shared planning views.
• Added list, Kanban, calendar, and timeline views over the same underlying work.
• Added task context including descriptions, dates, subtasks, comments, followers, attachments, dependencies, milestones, and recurring work where available.

Collect evidence, explore the workspace, and start from a useful outcome.

• Introduced Forms for building, publishing, sharing, and analysing response workflows with supported CRM mapping and destinations.
• Expanded shared reports with supported datasets, measures, filters, visualizations, drill-downs, and exports.
• Added workspace-level AI Chat and guided first-run onboarding for navigating evidence and preparing an initial agent.

Interpret voice activity in customer context and control what agents can do.

• Connected voice activity more closely with CRM customer and pipeline context.
• Added clearer operator controls for configuring supported agent actions and reviewing outcomes.
• Brought recordings, analytics, ownership, and follow-up together as separate evidence for operators.

More deliberate assisted work and automation across connected systems.

• Introduced AI Copilot for drafting and, with saved guardrails, selected lead-related actions.
• Expanded outbound webhooks plus control and observability around automated decisions.
• Kept automated decisions visible to operators so they could be reviewed in their workspace context.

Agent knowledge became more deliberate, reviewable, and reusable across the workspace.

• Expanded the handling of approved knowledge sources, retrieval context, and response guidance for conversational agents.
• Kept the source material, answer boundaries, and escalation expectations visible to the people operating the workspace.
• Made it easier to reuse a governed knowledge configuration across eligible agent and client-workspace setups.

A more connected path for turning event interest into useful customer context.

• Added foundations for branded registration pages that keep registrant details with the customer record.
• Connected event registration with the reminders and follow-up that can continue after an attendance decision.
• Made the event journey easier to operate as part of a wider customer workflow.

Multi-step lead journeys gained a clearer link to the customer record and the next action.

• Expanded foundations for no-code funnel paths that can capture a customer before a manual handoff is needed.
• Kept conversion context close to the CRM record and the follow-up that should happen next.
• Made it easier to think about a funnel as a customer journey rather than a disconnected campaign page.

Question-led lead capture began to guide customers toward a more relevant next step.

• Added foundations for question, score, and result paths that can surface the right recommendation for a lead.
• Connected quiz answers and outcomes with the customer context used in later follow-up.
• Made the captured result usable for routing, booking, assignment, or an approved workflow.

Outbound teams gained a more deliberate way to work through approved calling lists.

• Established foundations for working from an approved calling list with the relevant customer context available.
• Connected call outcomes with a follow-up path rather than treating a dialing session as isolated activity.
• Kept the customer record and the next operational step visible to the person making the call.

More governed knowledge and workflow operations inside client workspaces.

• Expanded agent knowledge operations inside client sub-accounts.
• Extended workflow and automation operations inside governed client tenants.
• Improved the operating context for agency teams supporting client workspaces.

More customer-facing experiences could be prepared for supported locales.

• Expanded localization foundations for supported product and customer-facing experiences.
• Improved the path to present relevant pages and communications in a supported locale.
• Kept customer-facing language choices tied to the workspace configuration that owns the journey.

Agency teams gained more context while working inside a client workspace.

• Expanded CRM enrichment inside governed client sub-accounts.
• Kept client records and enrichment work within their intended workspace boundary.
• Made it easier to review customer context before using it in a follow-up or automation.

A clearer way for agencies to set up and support separate client workspaces.

• Expanded sub-account creation, configuration, and authorized client-tenant support flows.
• Improved management of multiple workspaces without merging records, configuration, or connections.
• Kept the active client workspace clear when teams moved between accounts.

More deliberate email journeys around new leads, bookings, replies, and follow-up.

• Expanded triggered email foundations around customer events and the next appropriate message.
• Kept the contact, owner, and intended next action visible alongside the automated journey.
• Made it easier to review a customer’s communication context before the team continues the conversation.

Teams could begin client delivery from more complete, repeatable operating patterns.

• Expanded reusable starting points for client workspaces, lead journeys, and approved follow-up structures.
• Made it easier to adapt a proven configuration to a client without losing the separation of their records, brand, and work.
• Connected starter patterns with the templates, onboarding, and capability controls already available to eligible agencies.

More deliberate boundaries around who can do what in a client workspace.

• Added clearer controls for client membership, enabled capabilities, limits, and billing context.
• Helped agencies operate several client workspaces without merging their records or access paths.
• Kept the responsible client workspace visible when moving between operational surfaces.

More control over managed client plans and commercial relationships.

• Expanded agency billing foundations for client plans and commercial relationships.
• Clarified the separation between agency-managed and supported self-serve billing.
• Connected billing context more clearly to the client workspace it governs.

More control over the identity customers see in supported email journeys.

• Added broader customer-facing email branding and sender-configuration controls.
• Connected sender identity more clearly with the workspace and customer journey it supports.
• Kept delivery and sender readiness distinct from assuming an email was received or acted on.

Agency teams gained more control over the client operating experience they deliver.

• Expanded foundations for keeping a client’s brand, customer work, and workspace context distinct from another account.
• Made it easier to reason about a repeatable agency delivery experience without sharing records or workflow ownership.
• Connected the white-label experience to the client workspace where its real work happens.

A clearer path from initial agent configuration to controlled launch.

• Improved guided agent creation with clearer configuration stages.
• Made the setup path more explicit before teams test an agent with real customer scenarios.
• Connected initial configuration to the workspace and operational context that owns the agent.

More appropriate configuration options for supported agent experiences.

• Expanded language and voice-related choices for supported agent experiences.
• Made those choices part of the deliberate agent-setup path rather than an afterthought.
• Kept operators responsible for testing how the chosen configuration behaves in their use case.

Customer records gained clearer context for the person responsible for the next conversation.

• Improved how source details, qualification inputs, ownership, and recent activity could be reviewed alongside a customer record.
• Made the CRM a stronger handoff surface for agents, Inbox operators, booking owners, and follow-up workflows.
• Prepared the record model for later enrichment and governed client-sub-account work.

Teams gained a more connected place to draft, approve, and prepare customer email.

• Added foundations for drafting on-brand customer email with workspace context close at hand.
• Kept the editable message and customer record connected rather than separating campaign work from CRM context.
• Made review and approval part of preparing a message for the intended journey.

Faster automation setup and sturdier everyday operations.

• Introduced workflow-template foundations for common automations.
• Improved execution, error handling, recovery behaviour, and fixed reliability issues across relevant operations.
• Made common automated work easier to start from a reviewed baseline instead of a blank canvas.

Eligible subscription and billing actions gained promotional-code support.

• Added eligible promotional-code flows for applicable subscription and billing actions.
• Kept available promotions tied to the workspace and commercial context where they apply.
• Clarified that plan and billing screens remain the source of truth for a specific account.

Qualification and availability could guide a customer toward the right appointment path.

• Expanded scheduling foundations around availability, customer context, and the booking outcome.
• Made it easier to route a customer to the relevant calendar, person, or next step based on configured rules.
• Connected appointment details to confirmation, reminders, follow-up, and the customer record.

Teams could start from useful lead-flow views instead of building every report from scratch.

• Added more reusable reporting perspectives around lead source, response, booking, pipeline movement, and work ownership.
• Kept reporting tied to the underlying customer and activity context so operators could investigate a signal rather than only observe it.
• Made common operating views easier to adapt across workspace and client delivery scenarios.

More reliable connected accounts and shared workspace workflows.

• Improved the lifecycle for connecting supported external accounts to a workspace.
• Improved sending, synchronization, reconnect, disconnect, and use of connected events across modules.
• Clarified the account and workspace context for a connected integration.

More message activity could be reviewed in one shared workspace context.

• Expanded Inbox behaviour for messages arriving through supported connected channels.
• Improved shared conversation context as activity moved between automated and human handling.
• Kept connection health and the underlying channel as evidence for operators to verify.

More lead, response, booking, and task signals could be reviewed in one operating view.

• Expanded reporting foundations for reviewing lead-flow signals without separating evidence from the workspace that owns it.
• Connected operational signals with the customer, task, and next step that may need attention.
• Made it easier to spot where a lead journey was waiting before deciding how to act.

Start agent setup from a reusable configuration instead of a blank canvas.

• Added reusable AI template foundations instead of requiring every setup to start blank.
• Made it easier to carry a reviewed agent structure into a new workspace use case.
• Kept reusable setup distinct from the final instructions and guardrails for a live agent.

Lead capture could begin with more purpose-built questions, routing, and follow-up.

• Expanded reusable form patterns for inquiries, service requests, qualification, and customer intake.
• Kept submitted answers connected to the customer record, the intended owner, and the next approved action.
• Made it easier to use a consistent capture experience across campaigns, landing pages, and client workspaces.

More customer conversations could stay together in the workspace.

• Expanded Inbox handling across supported communication channels.
• Improved shared conversation context and transitions between automated and human handling.
• Made it easier to see the conversation alongside the customer and the next operational step.

Form responses could begin their life as useful customer context instead of an isolated submission.

• Expanded foundations for connecting a captured response with the built-in customer record.
• Kept response details, source context, and the next action available for a person or workflow to use.
• Made a form-driven handoff easier to review before starting an automated follow-up.

Better control over the customer records around shared customer work.

• Expanded CRM custom fields for business-specific customer attributes.
• Improved record import mapping and validation, plus supported export and reconciliation paths.
• Made customer-record transitions easier to review before they were relied on in a workflow.

A shared place to review and respond to customer conversations.

• Added Inbox foundations for reviewing and responding to customer conversations in one workspace view.
• Kept the customer record and relevant conversation context close to the response surface.
• Created a clearer starting point for responsible follow-up when a conversation needs an owner.

More confidence in the information an agent can use in a customer interaction.

• Expanded managed knowledge foundations for conversational agents.
• Made approved information easier to organize as part of agent configuration.
• Kept knowledge preparation distinct from an assumption that a live agent always has the right answer.

Booking workflows gained more deliberate preparation, reminders, and next steps when plans changed.

• Expanded the operating path around a confirmed appointment, from customer confirmation through preparation and follow-up.
• Kept reminder, reschedule, no-show, and owner context connected to the booking and customer record where configured.
• Prepared the calendar and automation surfaces for the routing capabilities that followed later in the year.

Operators gained a clearer view of relevant workspace consumption.

• Improved usage-credit visibility for operators monitoring consumption.
• Connected usage context more clearly to the active workspace and its enabled capabilities.
• Kept plan, billing, and current in-product usage details as the source of truth for availability.

Relevant changes and activity became easier for teams to notice.

• Added real-time notifications for relevant workspace changes and activity.
• Gave operators a clearer signal that work may need review or a next action.
• Kept notifications as prompts for review rather than proof that a downstream task was complete.

An unanswered call could trigger a clearer path back to a useful customer conversation.

• Added foundations for acknowledging an unanswered call and capturing the context needed to continue the conversation.
• Connected the recovery path with qualification, booking, human handoff, or approved follow-up work.
• Kept recovery activity attached to the customer record rather than losing it in a standalone text thread.

Agents could work with appointment availability and booking flows.

• Added calendar-aware actions for supported appointment availability and booking flows.
• Connected availability checks and booking work to the appropriate workspace resources.
• Brought scheduling into the same operating context as calls and follow-up.

More control over how workspace-associated inbound calls are handled.

• Expanded inbound calling behaviour for calls associated with workspace resources.
• Improved the operational path from an incoming call to its intended handling and follow-up.
• Kept the voice experience connected to the wider workspace model.

More useful call records for review and next-step decisions.

• Improved recording and call-evidence flows for review and follow-up.
• Made it easier to use the recorded call context when deciding what should happen next.
• Kept call evidence distinct from an assumed completion of downstream work.

Customer and call events became building blocks for repeatable automation.

• Expanded Workflow building so supported customer and call events could trigger repeatable operations.
• Connected voice outcomes with the broader automation surface.
• Created a stronger foundation for structured handoffs after a call.

Teams began reusing deliberate next-step patterns instead of rebuilding routine follow-up from scratch.

• Early workflow patterns brought together an event, decision, owner, and customer outcome in a repeatable structure.
• The work established a basis for later templates across lead response, booking, agent handoff, and client delivery.
• It made common operational work easier to explain, test, and adapt without hiding important decisions.

A clearer setup path between voice agents, calling resources, and integrations.

• Improved connections between voice agents, workspace calling resources, and supporting integrations.
• Expanded calling readiness and configuration behaviour for supported workspaces.
• Made it easier to assess whether a workspace was ready for the intended calling workflow.

More context for teams evaluating enabled modules before committing.

• Added trial-aware workspace and subscription flows.
• Improved onboarding context for teams assessing enabled modules.
• Connected plan evaluation more clearly with the active workspace configuration.

Common inbound-call jobs gained clearer questions, routing rules, and handoff expectations.

• The team shaped reusable conversational paths for intake, qualification, booking, and handoff around the needs of service businesses.
• Each path kept the caller’s answers and intended next action close to the customer and workspace context.
• These early playbooks informed the templates and guided agent setup that followed.

More structured customer and prospect context in the workspace.

• Expanded CRM records and the data used to organise customer and prospect activity.
• Improved the relationship between contacts, calling activity, and next-step work.
• Created a clearer operational record for outreach and follow-up.

A more deliberate way to work through approved audiences.

• Added campaign-oriented outreach foundations for controlled customer and prospect audiences.
• Connected campaign work with customer records, calling activity, and follow-up.
• Gave operators a more structured surface for repeatable outreach operations.

More visibility and control for workspace operators.

• Expanded subscription and usage controls for workspace operators.
• Improved the connection between commercial settings and the active workspace.
• Made plan-related operations easier to understand alongside enabled capabilities.

More complete creation, sign-in, recovery, and session foundations.

• Expanded account creation, sign-in, recovery, and session-related flows.
• Established a stronger basis for individual account ownership instead of shared access.
• Prepared the workspace for role-aware team collaboration.

Appointment scheduling started becoming a connected decision, not a standalone link.

• Early calendar work brought availability, qualification, the intended owner, and customer context into the booking path.
• The design considered how confirmed appointments, reminders, follow-up, and a changed plan should remain connected.
• This established the scheduling direction later expanded into calendar routing and booking workflows.

A clearer tenant boundary for records and configuration.

• Improved separation between workspaces so records and configuration stay in the intended tenant.
• Established the active workspace as an important context for customer data and connections.
• Reduced ambiguity in multi-workspace operations.

Bring teammates into the right workspace with more deliberate access.

• Added member invitations and role-aware collaboration controls.
• Established shared workspace navigation and team administration foundations.
• Made ownership and access management clearer for growing teams.

The first core tools for designing and evaluating conversational agents.

• Added core voice-agent configuration and testing experiences.
• Gave teams a starting point for creating repeatable phone conversation behaviour.
• Established controlled testing as part of preparing an agent for real traffic.

The first phone-based controls for inbound and outbound customer scenarios.

• Established phone-number and calling controls for inbound and outbound scenarios.
• Connected phone operations with the wider workspace and integration model.
• Created a foundation for configuring agents around the intended calling context.

The evidence layer for reviewing what happened on a customer call.

• Added product foundations for call recordings, transcripts, and post-call analysis.
• Made it possible to review conversation evidence after an agent or operator interaction.
• Created a basis for informed follow-up rather than relying on a call outcome alone.

Messages, customer context, and the next owner began to come together in one working view.

• The team explored a common place to review customer conversations beside their history, status, and follow-up.
• Early handoff behaviour focused on preserving the customer’s context when work moved from an agent to a person or team.
• This became the foundation for the Inbox and unified-communications work released later.

Early customer context and progress stages moved into one working surface.

• The prior-name product brought a customer record, visible progress stages, and the next action into the same early operating model.
• This prototype gave the team a shared place to explore customer context before the later CRM foundations were expanded.
• It marked the start of the record-and-pipeline direction carried into subsequent Spacebrain releases.

Early conversational behaviour was shaped around defined scenarios and review.

• The team explored the prompts, call paths, and escalation points needed for a useful customer conversation.
• Controlled testing made it possible to review agent behaviour before extending it into the dedicated builder experience.
• This work established the discipline behind the voice-agent capabilities that followed in September.

The early product gained a clearer home for customer work and configuration.

• The prior-name product separated customer context, setup decisions, and active work into a more deliberate workspace model.
• This established the operating context that later supported account access, team collaboration, and workspace separation.
• It was a foundational step toward keeping customer work organized as the product expanded.

Rebranding to Spacebrain.

• Spacebrain became the new identity for our connected operating system.
• The product brought demand capture, customer context, follow-up automation, and operational work closer together.
• The development history before this date remains part of the product story.

The connected product was prepared for more dependable real-world operations.

• Product work strengthened recovery paths, operating boundaries, and the ownership model around connected customer work.
• The team focused on making routine operations more dependable.

Early multi-client work began to separate each customer’s operating system from the agency’s delivery process.

• Product development explored separate client workspaces, customer context, and delivery ownership.
• The foundation made it possible to think about branded client experiences without blending records or active work between accounts.

Customer context, agent outcomes, and operational tasks began sharing a common flow.

• Product work connected customer context, agent outcomes, and the next action in the same operating flow.
• The prototype focused on continuity between conversations, records, follow-up, and the person responsible for the work.

The early system began to make the why and when of follow-up explicit.

• Development work explored decision points, ownership, and a repeatable next action around customer events.
• The aim was to make work reviewable instead of hiding important handoffs inside informal process.

Early lifecycle work connected a customer event with the next deliberate email or follow-up.

• Product development explored triggered communication around a lead, booking, reply, or handoff.
• The goal was to keep the message, customer record, responsible person, and next action connected.

Repeatable next steps begin to take shape around customer events.

• Early workflow work explored how a customer event could create an owned, repeatable next action.
• The focus was on connecting triggers, decisions, and follow-up rather than leaving handoffs to memory.
• These foundations informed the automation capabilities that followed.

Customer progress gained a clearer, shared path from signal to outcome.

• Product work explored visible stages, ownership, and an explicit next step for each customer.
• The emerging model made it easier to understand where work was waiting and who should act next.

Campaign entry points began to connect a visitor’s conversion with a useful next step.

• Product work explored focused lead-capture pages, multi-step journeys, and source-aware customer records.
• The early model linked a conversion to qualification, ownership, booking, or follow-up rather than a disconnected form submission.

A clearer model for the decision, owner, and next step at each customer moment.

• Product work mapped the moments where a customer moved from initial interest through qualification, booking, and follow-up.
• The underlying goal was to make the decision and handoff visible at every transition, before those moments became an operating pipeline.

The early experience started preserving the context behind a customer response.

• Development work explored a timeline where customer history, messages, and decisions could be understood together.
• The intent was to prevent a conversation from becoming a dead end when responsibility changed hands.

The early product began to treat booking as a connected outcome, not an isolated calendar link.

• Product work explored the questions, routing, ownership, and available next step that determine whether a customer should book.
• The intended flow preserved conversation and qualification context for the person receiving the appointment.

The conversation starts becoming part of the customer record, not a dead end.

• Early work explored keeping conversation context available to the person or workflow responsible for the response.
• Follow-up was treated as a connected next action with customer history, rather than an isolated reminder.
• This became a key principle behind the Inbox, CRM, and task experiences that followed.

Early agent work defined how useful automation should yield to a person.

• Product work explored controlled agent testing, fallback behaviour, and clear escalation paths.
• The product model treated the human responsible for the next action as part of an effective agent experience.

Early agent work began carrying a customer call outcome into the shared customer record.

• Product development explored how caller context, conversation outcomes, and useful call evidence could be captured together.
• The focus was on keeping a call outcome useful to the team responsible for the next customer interaction.

Early conversational-agent work defined how an agent should use approved business knowledge.

• Product development explored how agents could use approved context, clear instructions, and business-specific language in a customer interaction.
• The work focused on giving an agent reliable boundaries for its answers before broader voice and handoff flows were designed.
• These early learnings carried into the voice and AI capabilities released later in 2025.

The early product model began to distinguish responsibility from shared access.

• Development work explored how customer context and next steps could remain visible to the right person or team.
• The focus was on making handoffs accountable without losing the history needed to continue the work.

The next customer commitment started becoming work a specific person could see and complete.

• Product development explored owned tasks, a clear status, and the customer context needed to carry a commitment forward.
• The early model supported a more accountable handoff across teams than an unstructured reminder or shared inbox alone.

The early product model starts to make ownership of the next step explicit.

• Product work focused on making a customer promise, assignment, or follow-up visible to the right person.
• The emerging model tied work to its context, including the customer, conversation, and intended outcome.
• This became an important basis for the product’s later team, task, and workflow capabilities.

The early CRM direction connected the customer record with the work around it.

• Product work mapped customer information, conversation context, operational work, and the next action together.
• The goal was a usable shared record rather than isolated fields or disconnected customer tools.

Early inquiries and form responses began to enter the shared customer record with their source intact.

• Product work explored capturing customer details and source context in the same record used for follow-up.
• The foundation connected an incoming inquiry with qualification, ownership, and the next action rather than leaving it in a standalone form tool.

A shared system for customer context takes shape.

• Early 2025 product work established the CRM design direction: one shared customer record instead of fragmented tools and context.
• The foundation linked customer information, conversations, operational work, and the next action around that record.

Early knowledge work made clear what an agent could answer, when it should pause, and how a person could continue the work.

• The team refined answer boundaries, escalation guidance, and the operator context needed after an automated conversation.
• Knowledge was treated as an operating asset with sources, rules, and a useful route back to a person—not a static document collection.
• These principles carried into the later Knowledge Hub, conversational agents, and shared Inbox experiences.

Early knowledge-base work connected approved source material with the answers an agent could use.

• Product work explored how policies, service information, and operating guidance could be organized for conversational use.
• The approach kept source material, retrieval context, and a safe next action close together.
• This laid the groundwork for the knowledge sources and agent controls that followed.

The team tested how grounded context could make automated customer conversations more useful.

• Early RAG experiments paired an incoming question with the most relevant approved context rather than relying on a generic response.
• The work focused on relevance, answer limits, and knowing when to ask for more context or hand off to a person.
• It established the retrieval direction that later became part of the platform’s managed agent knowledge.

The first pieces of a shared customer system come together.

• Early product development focused on keeping customer context, work, and the next action in one connected place.
• The connected model brought customer progress and operational work into the same flow.

Customer records began to carry visible progress, ownership, and a deliberate next step.

• The early CRM model brought a customer’s activity, status, and responsible person into the same operating view.
• The goal was to make handoffs and pipeline movement explainable rather than leave customer work in disconnected tools.
• This design direction later informed CRM records, tasks, dashboards, and automation.

The product shifted from a call outcome to a durable view of the customer relationship.

• Early CRM work linked contact information, conversation context, notes, and the next action around a shared customer record.
• The timeline made it easier for a new owner to understand what happened before they picked up the work.
• This was the beginning of the connected customer-context model that later supported calls, forms, messages, bookings, and tasks.

Early voice work made a customer conversation useful after it ended.

• The product began retaining the key reason for a call, its outcome, and the intended next action for review.
• This helped operators test whether a voice interaction was useful instead of treating a completed call as the end of the workflow.
• The work later informed recordings, transcripts, analysis, CRM context, and voice-triggered automation.

The initial voice-agent direction expanded into defined jobs, prompts, and test conversations.

• The team explored the conversational paths for common inbound work: answering, qualifying, routing, booking, and escalation.
• Configuration work focused on giving each agent a clear job and making its behaviour reviewable before it was trusted with live demand.
• These ideas became the basis for the voice-agent builder and guided setup that followed under Spacebrain.

The earliest product work focused on making an inbound customer call useful from the first response.

• The product began with conversational-agent experiments for answering calls, understanding a request, and deciding the next step.
• The core question was practical: could a customer receive an immediate, useful response while their context stayed available to the business?
• This established the voice and lead-response direction for the product.

The product foundations are underway.

• This is the start of the documented Spacebrain product history.