A straight answer for buyers and operators: Peak Demand’s Voice AI can read permitted Lofty records, create supported tasks/appointments where your Lofty plan allows, capture and qualify leads, route calls, and confirm results — while handing off to a human when the workflow needs brokerage judgment or scheduling permissions.

What can Voice AI actually do with Lofty?
Plain-English list of real actions you can expect once Peak Demand connects Voice AI to Lofty — and the boundaries you must accept.
Typical supported actions
Peak Demand’s voice agent can: read permitted contact and listing information from Lofty; capture structured lead and inquiry details from a caller and create a lead record; create tasks and reminders; update basic contact fields; route the call or create an internal ticket for follow-up.
- Read permitted contact, listing and status data to answer caller questions.
- Create new leads/opportunities and attach captured notes or audio transcripts.
- Create tasks, reminders or tickets for agents to action.
- Attempt appointment/showing creation only where Lofty’s API and account permissions allow.
What Peak Demand will not do on its own
We do not authorise the voice agent to make pricing, legal, lending, tenancy or negotiation decisions. If an action requires brokerage judgment (price changes, contract acceptance, legal advice), Peak Demand confirms the caller’s request, records it into Lofty as a task or lead, and immediately routes to a human agent.
- No unilateral pricing or listing edits without human sign-off.
- No tenancy or legal decision-making by the voice agent.
- Complex multi-party scheduling or conditional negotiations escalate to a human.
What happens when a caller wants to book, change or check something?
Real caller examples and the exact sequence of what the voice agent does, what it reads from Lofty, and what it writes back.
Booking a showing (caller says: “I want to see 123 Main St this Saturday at 2pm”)
How the interaction flows: The voice agent confirms the property and caller identity, checks listing and agent availability via Lofty (read). If your Lofty account exposes appointment creation via the API and calendars are connected, Peak Demand will attempt to create the showing and record it in Lofty (write/scheduling conditional). The agent then tells the caller the booking status and email/text confirmation details. If scheduling isn’t available or the requested slot conflicts with business rules, Peak Demand creates a task in Lofty and routes it to the listing agent to finish the booking.
- Verify caller name and contact (limited PII retrieval and immediate confirmation).
- Read listing availability and assigned agent from Lofty (read) — vendor_api.
- If allowed, create an appointment/showing (write; scheduling conditional) and confirm to caller.
- If not allowed, create a task in Lofty and notify the agent to complete booking.
Changing or cancelling an appointment
The agent looks up the appointment by caller identity or confirmation number (read). If the API and permissions allow edit operations, Peak Demand will update the appointment and send a new confirmation.
- Lookup by confirmation or contact (read).
- Attempt update via API if write/scheduling scope is available, otherwise create a flagged task.
- Always confirm the outcome verbally, and follow with an SMS or email if configured.
What can the agent update or route?
Practical updates and routing actions that keep agents informed and Lofty records current.
Updating contact and lead fields
When callers provide new details — corrected phone, email, preferred contact time, or buying timeline — the voice agent writes those fields to the lead/contact record in Lofty. Peak Demand validates formats (email, phone) before writing and captures a short transcript for audit.
- Validate and write new contact fields to Lofty (write).
- Attach the call transcript and confidence metadata to the record for agent review.
- Do not change lead status to negotiation or closed without human confirmation.
Routing to the right team or agent
Peak Demand uses caller intent, property location and listing assignment to route leads. The agent can create a route or notify an on-call agent in Lofty by assigning the lead or creating a task. For after-hours or general intake, the voice layer captures full context and creates a prioritized task or notification in Lofty.
- Assign lead to an agent or create a follow-up task in Lofty.
- Use business rules (office, geography, listing agent) to determine routing.
- When routing is ambiguous, capture the caller’s preference and escalate to an on-call human.
When should a human take over?
Clear triggers that move the call from Voice AI to an agent — and examples that matter for real estate teams.
Legal, pricing, or negotiation issues
Any request that touches pricing strategy, concessions, contract terms, tenancy disputes or legal advice must be sent to a human. Peak Demand will capture the caller’s request, create a detailed task in Lofty, notify the appropriate agent, and offer to transfer the caller.
- Price changes, offer acceptance or contract edits → immediate human handoff.
- Tenant disputes or eviction-related calls → human-only.
- Complex multi-party scheduling or conditional offers → human.
Low-confidence or ambiguous responses
If the voice model’s confidence score falls below a configured threshold — for example, ambiguous address, conflicting availability, or unclear identity — the system offers to connect the caller to a human. The call, transcript and Lofty context are attached to the resulting task for seamless handover.
- Configured confidence threshold triggers human transfer.
- All context is saved in Lofty so an agent picks up with full history.
Implementation reality: API access, permissions, AWS middleware and safety
The technical constraints that determine which workflows are fully automated and which are conditional or human-assisted.
Lofty API status and permissions you must confirm
Official Lofty documentation confirms an API/developer surface with authentication via REST using OAuth 2.0 or an API key, read=Yes and write=Yes. Scheduling (appointment/showing creation) and webhooks are conditional depending on account plan, brokerage permission and calendar linkage. Peak Demand will validate the exact endpoints, scopes and permissions during scoping and implement safeguards to avoid unauthorised actions.
- Authentication: OAuth2 or API key — per Lofty developer docs.
- Read and write are supported, scheduling and webhooks depend on your Lofty account and brokerage permissions.
- App authorisation, brokerage approvals and API tier may be required for write/scheduling access.
AWS middleware, validation and MCP
Peak Demand uses an AWS-based middleware layer between the voice model and Lofty to enforce business rules, control authentication, manage retries, redact PII as required, and produce audit logs. We also apply a Model Context Protocol (MCP) to scope what the voice model can ask for: MCP supplies precise contextual metadata (which listing, which contact, permitted fields) so the model only requests records and fields approved by policy.
- Middleware enforces validation (format checks, business rules) before any write.
- Retries, back-off and fallbacks (create task rather than fail booking) are implemented at the middleware layer.
- MCP defines and limits the context exposed to the voice model to reduce overreach and improve safety.
Operational checklist before you connect Peak Demand to Lofty
A short, actionable list of what your team will need to verify so workflows behave as expected.
Permissions and accounts
Confirm app authorisation path (OAuth or API key), required API scopes, and whether your brokerage must approve third-party integrations. Verify which Lofty plan features (appointments, webhooks) are enabled.
- Create or approve a Lofty integration user and confirm scopes.
- Brokerage sign-off if required by your account or compliance team.
- Decide whether to grant write/scheduling scope or limit to read-plus-task creation.
Customer experience and compliance
Decide voice prompts for consent, whether you want to record calls, what fields the agent may write to, and your escalation rules. Confirm data residency and subprocessors for your organisation’s legal and procurement teams.
- Recording consent and notification scripts for callers.
- Retention, regional hosting and subprocessors to review with legal.
- Define human-handoff rules and confidence thresholds.
Related Peak Demand resources
Industry and AI sources reviewed
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
Maybe — Lofty’s official developer surface supports read and write operations, and appointment/scheduling is conditional. If your Lofty account and brokerage permissions expose the appointment endpoints and calendars are connected, Peak Demand can attempt to create showings via the API. Where scheduling endpoints aren’t available, Peak Demand will capture the appointment details and create a task in Lofty for an agent to complete the booking.
Official reference: Lofty official API/developer source
No. Peak Demand’s implementation prevents the voice agent from making pricing, legal or contract decisions. If a caller asks for a price change or contract modification, the agent will record the request in Lofty and route it to the appropriate human for review and approval.
Lofty’s API uses REST authentication via OAuth 2.0 or an API key, per the official documentation. Peak Demand will use the approved method during setup and request only the scopes needed for the agreed workflows.
Official reference: Lofty official API/developer source
Yes. Peak Demand’s 24/7 Voice AI captures full lead details, creates a lead record or a follow-up task in Lofty, and routes it based on your routing rules. See our AI receptionist and missed‑call recovery resources for real estate to design the experience.
We place an AWS middleware layer between the voice model and Lofty to control authentication, field‑level writes, redaction, retries and audit logs. Every interaction can be attached to the Lofty record with transcripts, confidence scores and error details for traceability.
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
