One account. Five jobs.

One agent per number

Phone number, agent ID, voice, language, first message, and script — independently configured and toggled active or inactive.

Live transfer to a person

Transfer number, sensitivity, custom trigger phrases, announcement, and retries so the handoff sounds deliberate.

Call duration cap

Set a maximum conversation length in minutes so calls cannot run away.

Structured data from the conversation

Define extraction fields with an instruction and type (string, boolean, and more). After the call, Grepiv fills them from the transcript.

Pre-call CRM enrichment

An append webhook runs before the agent speaks. Template the body with caller_id, to_number, and other call variables so the AI already knows who is calling.

Conditional lead creation

Create a CRM lead only when extracted variables match rules — equals, contains, exists, numeric compares, AND / OR.

Post-call AI texting

If a condition matches, send an SMS after the call using a message template and a chosen from-number.

Post-call webhook workflows

Visual workflow builder: chain HTTP webhooks with conditions, headers, body templates, and a test / dry-run from the editor.

Mid-call tools on the number

Arm account-level tools so this inbound line can fire APIs or inject knowledge during the call.

Reusable outbound configs

Name, agent, voice, language, script, first message, originating number, and max duration — same depth as inbound.

Auto-dial on new lead

Turn on trigger-on-lead-created and Grepiv places the follow-up the moment a matching lead arrives.

Source guardrails

Exclude inbound, webhook, manual, outbound, or API sources so you never robocall someone who just called you. Inbound is excluded by default.

Pipeline and form targeting

Restrict the config to a lead pipeline and to specific lead forms.

Place a call from the dashboard

Dial any number with an agent, voice, script, variable extraction, and tools. Save the setup as a template.

API-initiated outbound

Start a call from your systems with to-number, agent, and optional Twilio overrides.

Variable extraction and tools

Outbound calls extract fields and can fire the same mid-call tools as inbound.

Embeddable iframe

Copy an embed snippet or a direct widget URL. Public initiate endpoint for unauthenticated visitors.

Brand the widget

Title, subtitle, colors, button shape and size, fonts, and animations. Default title: Grepiv AI Assistant.

Audio and ICE control

Gain, echo cancellation, noise suppression, AGC, buffer size, and custom STUN / TURN servers.

Same agent stack

Voice agent, voice, max duration, extraction fields, and tool assignment. Same as phone calls.

Voice library

Search the catalog and play a preview in the dashboard.

Picker everywhere it matters

Inbound, outbound, and WebRTC editors all use the same voice picker — paste an ID or browse.

Per-number SMS agents

Prompt, agent ID, and an account default that answers any number without its own configuration.

Sync with call configs

Link SMS to the inbound or outbound config on the same line so voice and text share context.

Prompt enhancer

One click reorganizes a prompt into a clean AI / user turn structure.

Auto-reply

When enabled in settings, inbound SMS is answered automatically through the Twilio webhook.

WhatsApp

Send and receive WhatsApp on your own numbers as plain text. The send API also accepts Twilio Content Templates.

Extract variables from texts

Same instruction-and-type fields as voice, evaluated on the conversation.

Conditional leads and webhooks

Create a lead or fire HTTP webhooks only when conversation conditions match.

Rich context injection

The SMS agent sees lead details, recent calls, tasks, business hours, and open appointment slots. Follow-ups only resend what changed.

Threads, not just phone numbers

A conversation can exist before a lead. Identity prefers an explicit lead or thread, then the phone. One number can belong to more than one lead over time.

Live inbox

New messages land without a refresh. The desk also polls so a dropped socket does not go dark.

AI replies per thread

Turn AI off on one conversation when a person takes over. Account auto-reply stays as you set it.

Intent-based lead creation

When lead creation is enabled on the SMS config, buying or selling language in the thread can create a lead once.

Jump to the lead

Open the record from the thread, or keep working a conversation that has no lead yet.

Pipelines you name

Intake, consultations, new quotes, renewals — add the pipelines your desk runs, each with its own form and fields.

Lead forms

Name, color, description, which extracted fields to show, which sources are allowed, and your own custom fields (name, type, required).

Webhook intake

A tokenized POST per lead configuration so a site or CRM can drop a lead in. Optional auto-call on arrival.

Manual and API create

Add a lead from the dashboard or your systems. Optional immediate outbound call.

Repeat callers do not become six leads

Each inbound number chooses what happens when the caller already has a lead: create a new one, merge the call onto the existing one, or skip. In the dashboard a matching phone or email is a warning, not a block.

Extraction fills your form fields

Map an extracted variable to a lead field, so a call that captured firstName and phone lands in the Full Name and Number columns instead of a row of dashes.

A running summary on the lead

Every completed call updates a summary kept on the lead — not only the ones that booked. The next call reads it back, so the agent opens knowing the last conversation.

Dynamic lead details

The field set is whatever your inbound, outbound, and SMS configs extract, plus form fields and anything already stored.

Every lead says where it came from

Inbound call, outbound call, webhook, added manually, API, AI SMS, and the chat widget. The list filters by the first five.

History by phone

Pull every lead and call tied to a number when the same person comes back.

Account calendar

Week view and today's timeline across every lead. Book from the week view. Filter by status.

Statuses that match a busy desk

New, In Progress, Completed, Missed, Cancelled, No Answer.

Book from the dashboard

Pick a lead, title, date, start time, duration (15 to 120 minutes), assignee, and notes. Delete an appointment from the lead record.

Book from the call

Voice-agent webhook can create, reschedule, or cancel an appointment from extracted data.

Working hours

Account window plus per-weekday overrides. Bookings outside hours are rejected. The AI knows open slots at call start.

Round-robin staff

Staff agents (name and phone) are the people the AI assigns to. Unassigned bookings from a call rotate and skip busy slots. The calendar also lets you pick someone.

Three trigger modes

Fire immediately on a phrase, ask then confirm (with refusal phrases), or inject knowledge with no HTTP call.

Rules, AI, or both

Your server decides from speech, the voice agent decides, or both. Sync and export the tool to the voice agent.

Full HTTP shape

Method, URL, headers, path / query / body params. Values can be an LLM prompt, a dynamic variable, or a constant. Optional regex extract.

Assign per config

Arm tools on inbound numbers, outbound configs, and WebRTC calls without rewriting them.

Pre-call append webhook

Fetch CRM context and inject it before the agent greets the caller.

Post-call workflows

Visual canvas on inbound: Start node, connected webhooks, conditions, body templates with placeholders, test from the editor.

Lead ingestion webhook

Token-authenticated POST so any site or CRM can drop a lead into a form — and optionally auto-dial.

SMS and WhatsApp webhooks

Same condition + template pattern when a text conversation hits a rule.

Initial context for the agent

Machine-to-machine lookup: known lead, appointments, and bookable slots injected at the start of a call.

Delivery log for every webhook

One row per attempt: what was sent, what came back, the status code, and how long it took. Attempts that never fired are logged too, with the reason — a webhook skipped because its conditions did not match is the case most often mistaken for a broken one.

Account API keys

Long-lived eko_… keys for voice-agent and integration auth — separate from dashboard sessions.

Live operations dashboard

Total, active, completed, and failed calls. Inbound vs outbound. Success rate. Average durations. Lead count. Numbers with AI SMS on.

Charts that match the work

Seven-day inbound vs outbound volume, new leads this week, leads by source, and a recent-activity table.

Call history

Search and filter inbound / outbound. Open any call for summary, transcript, and recording.

Message inbox on the call

SMS and WhatsApp tabs on the call detail, with an AI auto-reply toggle and the sending number.

Multi-tenant accounts

Every lead, call, config, and key is scoped to the account. Team members inherit the owner’s workspace.

Roles

Admin (full), member (permission-gated), and a platform super-admin for operators.

Module permissions

Inbound, outbound, and leads — hide the nav and block the API when a member is turned off.

Company profile

Company name, industry, address, city, country — shared across the team.

One clock for the whole account

Each user sets an IANA timezone, or uses the browser’s. The account’s timezone is also the clock the agent is told about, so the date resolved on a call and the date a webhook sends seconds later agree.

Bring your own numbers

Connect your own Twilio account with an account SID and auth token, then fetch, tag and multi-select the lines Grepiv may use. Existing numbers can be ported into Twilio and kept.

Super-admin console

Operators list every tenant and edit that account’s Twilio settings, inbound configs, WebRTC configs, and AI SMS config.