AI Engine · Technical overview

The engine behind every answer

One session across voice, text, email, and chat. Grounded in your knowledge, run by your procedures, governed by guardrails, and backed by people.

DWG · WL-ENGINE-01SCALE · NTS · REV CVOICE01SMS02EMAIL03CHAT04SESSIONGUARDRAILSPROCEDURESKNOWLEDGEONE CONTEXT · ONE QUEUE · EVERY CHANNELWORK ORDERSTOURS & BOOKINGSTEXTS & EMAILSPMS / CRM UPDATESTRANSFERSHUMAN TEAMWARM TRANSFER · ESCALATION CHAININPUTCHANNELSFIG. 1 — WAYLINE ENGINE
Anatomy of a conversation

Six stages, every time

01

Pick up

Every AI-answered call opens with a recording disclosure, then a greeting in your property's name. Texts, emails, and chats land in the same queue.

02

Understand

A real-time speech model listens and speaks in one pass, so callers can interrupt and the conversation still flows. English and Spanish, switched mid-call.

03

Ground

Answers come from your approved knowledge, live listings, and property data. If it isn't in there, the agent doesn't make it up.

04

Follow procedure

The scenario is matched to your Procedure for that property, and the steps are followed in order.

05

Check guardrails

Fair Housing rules, verbatim answers, and emergency handling outrank everything else in the conversation.

06

Act or hand off

Book, create, update, send, or transfer. When a person is needed, the escalation chain runs until someone picks up.

Procedures

Your playbook, in plain English

You don't write prompts or build bots. You tell Wayline how your team handles a situation, scoped to the whole portfolio, a property group, or a single building, and the engine follows it.

  • Scenario and instructions, written like an SOP
  • Scoped by organization, property group, or property
  • Knowledge Q&A with approved, published, and verbatim answers
  • Access levels by audience: residents, prospects, owners, staff
procedure · after-hours-no-heatActive
scope
Maple Court · all units
scenario
Resident reports no heat between 6 PM and 8 AM, October through April.
instructions
  1. Ask if any unit is below 55°F or anyone is at risk.
  2. If yes, treat as an emergency and start the on-call chain.
  3. If no, confirm thermostat settings and breaker.
  4. Create a work order, priority high, and text the resident a summary.
  5. Read verbatim: “For your safety, please do not use the oven to heat your apartment.”
escalate_to
On-call maintenance → Property manager → Wayline team
Guardrails

Rules that outrank the conversation

Some rules are yours. Some apply to every Wayline customer. All of them sit above anything a caller says.

01

Fair Housing first

Questions about vouchers, income or credit criteria, criminal history, or neighborhood demographics always go to a person, with a set response. It is the highest-priority rule in every conversation.

02

No invented answers

The agent never promises a service, appointment, or listing that isn't in your knowledge, procedures, or live inventory.

03

Verbatim when it matters

Mark an answer as verbatim and it is read word for word. Legal language and safety instructions stay exactly as written.

04

Emergencies skip the small talk

No clarifying questions when it's urgent. Your emergency procedure runs immediately, or it escalates as a maintenance emergency.

05

Email waits for approval

Outbound email is drafted for your team to approve by default. Auto-replies are switched on per channel, by you.

06

Knows when it's stuck

Poor connections and conversations going in circles are detected and handed to a person instead of looping.

One context

Every request, in the building it belongs to

Calls, texts, and emails are matched to the resident, unit, and property before the first answer. The engine reads and writes to your property management system, so the work order, guest card, or tour is where your team expects it.

6 FL01 TOUR REQUEST · 4B02 LEAK UNDER SINK · 2A03 PACKAGE ROOM ACCESS04 LOCKOUT · LOBBYELEVATION A · NORTH · 1:2004 ACTIVE · 0 WAITING
Human escalation

The model decides. Code makes sure.

When a person is needed, the agent makes one decision: escalate, and what kind. From there a deterministic chain you configure takes over, calling, texting, and leaving voicemail with retries while the caller holds, and logging every attempt.

  1. 01
    Warm transferStaff member screened, then bridged
  2. 02
    Call on-callAttempt 1 of 3
  3. 03
    TextWith summary + callback
  4. 04
    VoicemailRingless drop
  5. 05
    Wayline team24/7 human coverage

Scored, every session

Each conversation is scored for accuracy, tone, instruction adherence, and latency, with a human review status your team can see.

Three agents, one brain

A real-time front desk, a back-office agent that works tasks to completion, and an assistant your staff can text. Shared tools, knowledge, and rules.

English and Spanish

Detected and switched mid-conversation, across every channel.

Voice SMS Email Website chat

Put the engine on your phone lines

We'll load your knowledge and procedures and run it against real scenarios from your buildings.