Plain-English guide for law firms: what Peak Demand’s Voice AI can and cannot do with Centerbase, with concrete caller-to-workflow examples, confirmations and handoff rules.
What can Voice AI actually do with Centerbase?
Short answer first: Peak Demand’s Voice AI can handle call answering, structured intake, existing-client routing and permitted record changes in Centerbase — but only within the firm’s API permissions and the supported record model. Below are the most common, practical workflows firms ask about.
High-level capability summary
Peak Demand’s agent listens to callers, captures structured data, looks up permitted context in Centerbase (contact, matter, recent tasks), and performs supported actions such as creating new contacts, opening intake matters, logging tasks or notes, and routing callbacks. For scheduling or calendar writes, implementation depends on whether your Centerbase environment exposes event/task endpoints and whether the firm grants write permission.
- Read permitted records: contacts, matters, tasks and basic matter metadata.
- Write permitted records: create/update contacts, matters and tasks when API access is granted.
- Conditional scheduling: event/task model use depends on firm API and calendar integrations.
- Human escalation for judgement, conflicts, or fee/representation decisions.
How Peak Demand differentiates execution
We do not treat Voice AI as a blind write engine. Peak Demand’s AWS middleware validates each request against business rules, enforces field-level permissions, retries failed writes, and stores an audit record of the entire interaction.
- Business-rule checks before any write (conflicts, duplicate contacts, matter associations).
- Field-level masking so sensitive fields are never exfiltrated into the voice layer.
- Clear confirmation prompts that repeat the intended system action in plain language.
What happens when a caller wants to book, change or check something?
Booking language is common. Firms ask: can a Voice AI schedule a consultation in Centerbase? The genuine answer depends on your Centerbase setup and API permissions. Here are practical caller-to-system examples.
Caller: “I’d like to book a consultation.”
What the agent needs: caller identity (existing client or new), preferred time windows, matter type, and any urgency indicators. Permitted system actions: create a new contact or match to an existing contact, create an intake matter or task, and — where enabled — create an event/task that appears on staff calendars.
- If caller is new: capture name, phone, email, matter type; create a contact and intake task in Centerbase.
- If scheduling endpoint is available and allowed: create an event/task or mark availability and return a confirmation reference.
- If calendar sync or firm policy prevents automatic booking: the agent will schedule a staff callback and create a task in Centerbase.
Caller: “Change or cancel my consultation.”
What the agent needs: caller identity, appointment reference or approximate time, and new preferred times. Permitted system actions: look up matching events/tasks in Centerbase and update or cancel where write permission exists.
- If an event exists in Centerbase and API writes are allowed: update or cancel and confirm to caller.
- If event is controlled by an external calendar with no API path: log a clearly labelled task and advise caller a staff member will.
What can the Voice AI agent update or route in Centerbase?
Operators need to know which record changes are practical and safe to automate. Below are the common record types and routing actions Peak Demand implements.
Contact and matter creation/updates
Common permitted writes include creating a new contact, updating phone/email fields, and creating an intake matter or adding notes to an existing matter. Peak Demand’s middleware enforces duplicate checks and asks clarifying questions before a write.
- Create a contact with name, phone and email.
- Update contact fields such as preferred contact method or best callback window.
- Create a new intake matter with basic metadata (matter type, brief description).
Tasks, notes and routing to responsible staff
Rather than changing substantive legal data, most automated actions create tasks or notes tied to matters so staff can follow up. The agent can assign tasks, set priority, add intake summaries, and route to the responsible lawyer or intake team.
- Create an intake task with structured summary and urgency flags.
- Assign the task to a staff member, practice group or a triage queue.
- Add a short, timestamped call summary to the matter record for later review.
When should a human take over?
Not every call should remain fully automated. Peak Demand defines clear handoff thresholds so that legal judgment, identity verification, and ethical obligations remain with humans.
Triggers for immediate human escalation
The Voice AI will hand off or summon a human agent when the call requires conflict checking, fee or representation decisions, disclosure of privileged information, or an identity verification that the firm requires a live verifier to perform.
- Potential conflict of interest discovered during intake.
- The caller asks for legal advice beyond intake questions.
- The request involves sensitive personal data that requires human consent or verification.
When partial automation is appropriate
For many operational tasks — missed-call recovery, callback scheduling, follow-up reminders and basic routing — the agent completes structured steps in Centerbase and then places the matter into a workflow for human action. This reduces hold time and keeps legal decisions human-led.
- Agent collects intake, creates a task and routes it to intake staff for a human to complete representation decisions.
- Agent confirms appointment details but informs caller a human will complete final confirmation if firm policy requires it.
Implementation reality: API, permissions, middleware and safety
Firms evaluating Voice AI need to understand the real prerequisites and controls. Centerbase provides a developer API surface that supports REST credentials, reads and writes, and an event/task model for scheduling — but access is account- and permission-dependent. Peak Demand’s practical deployment model closes the gaps.
API access and permission caveats
Centerbase documents a REST developer API with authentication using API credentials. Read and write operations are supported where the firm enables them. Scheduling is conditional: Centerbase supports events/tasks, but whether the Voice AI can create calendar events depends on how your firm configures calendars and grants API write scopes. Peak Demand’s implementation plan starts by validating your account credentials and a permission matrix.
- Authentication: REST / API credentials per Centerbase documentation.
- Read: permitted (contacts, matters, tasks) when scope allows.
- Write: permitted for same records when scoped and authorised.
- Scheduling: possible via event/task model but must be validated in your environment.
Role of AWS middleware and Model Context Protocol (MCP)
Peak Demand uses an AWS middleware layer to manage authentication, run business rules, enforce field-level permissions, validate inputs, and keep an auditable trail of every voice interaction. The system passes structured context (call metadata, matched Centerbase record IDs and intent) to the model using a Model Context Protocol (MCP) pattern so the agent makes decisions with the minimum necessary data.
- Middleware handles retries, exponential backoff and failure categorisation.
- MCP carries only permitted fields to the model for intent and entity resolution; sensitive fields remain masked.
- Full audit logs and a replayable transcript are stored for QA and compliance review.
Operational checklist: What to validate before you go live
Before deploying, confirm these items with IT, intake and practice leads so the Voice AI operates within your firm’s controls.
Permissions and scope
Ensure the API credentials provided to Peak Demand are scoped only to the necessary records (contacts, matters, tasks) and that calendar/event writes are explicitly allowed if you want automated booking.
- Provide least-privilege API keys for production and a separate key for staging.
- Confirm whether calendars are managed in Centerbase or an external provider.
Intake scripts, confirmations and handoff rules
Work with Peak Demand to author intake prompts, confirmation language, urgency flags and exact human-handoff triggers. Keep language firm-led and non-advisory.
- Draft caller prompts that collect the minimum required information.
- Define human-handoff thresholds for conflicts, fee/representation and identity verification.
Related Peak Demand resources
Industry and AI sources reviewed
- Centerbase official API/developer sourceCenterbase
Privacy, cybersecurity, contractual, records, and sector-specific obligations vary by jurisdiction and connected system. This article is operational guidance, not legal advice; organizations should confirm applicable requirements with qualified professionals.
Frequently asked questions
Yes — but only if the firm provides API credentials with write permission for those record types. Peak Demand will confirm duplicate checks and business rules before creating a contact or an intake matter, and will always confirm the creation with the caller.
Official reference: Centerbase official API/developer source
Possibly. Centerbase supports an event/task model that can be used for scheduling, but whether bookings can be written directly depends on how your firm configures calendars and whether API write access is granted for events.
Official reference: Centerbase official API/developer source
Conflict checks are a standard handoff trigger. If the Voice AI identifies a potential conflict from caller responses or existing Centerbase records, it will not complete representation actions; instead it will create a priority task and escalate to a human reviewer. Final conflict determinations and representation decisions remain with your staff.
Peak Demand logs all voice interactions and every attempted change. The AWS middleware performs retries with exponential backoff for transient API failures; persistent failures generate a flagged task in Centerbase for human follow-up.
Possibly — this depends on your jurisdiction and client consent requirements. Peak Demand supports configurable recording consent prompts and retention policies, but firms must confirm data-residency, retention and subprocessors with their legal and compliance teams. Do not assume recordings or cross-border transfers are permitted without review.
Engineer the integration layer before scaling Voice AI
Peak Demand designs the APIs, logic bridges, validation, fallback, observability, and human-escalation infrastructure required for dependable Voice AI operations.
Schedule a discovery call
