Read your results

Start in Analytics

Open Analytics from the sidebar for campaign-level summaries. Use Calls when you need a single conversation or transcript.

Filter by campaign or flow name you set during planning. Consistent naming pays off when you compare weeks side by side.

Metric definitions

• Answer rate: connected calls divided by attempted calls.
• Connected minutes: billable time on answered calls—the same basis as your invoice.
• Calling cost: connected minutes multiplied by your per-minute rate.
• Attributed orders: orders linked to a qualifying call inside your attribution window.
• Attributed revenue: order value for those attributed orders.
• Revenue-to-cost multiple: attributed revenue divided by calling cost; unavailable when cost is zero.

Attribution caveats

Attributed revenue ties orders to calls that happened within a window you configure. It is a reporting link—not proof the call caused the purchase.

Shoppers who buy through email, ads, or return on their own may still appear as attributed if the order falls inside the window. Read trends, not single orders, when tuning programs.

Attributed revenue is order value under your rules—not margin, not LTV, and not a guarantee that the call caused the purchase. Use it to compare programs, not to forecast finance.

Home dashboard

Home shows setup readiness and a snapshot of recent campaign activity. Use it for a daily glance; use Analytics for deeper cuts.

If setup items remain incomplete, finish store profile and phone steps before interpreting early metrics.

Voicemail and connected time

Voicemail detection ends the call without leaving a message. Treat answer rate and connected minutes separately when judging script changes.

A spike in short connected minutes may mean more voicemail or hang-ups—not necessarily better conversations.

Review transcripts

Sample five answered calls per week. Note where the rep searched for facts, stumbled on policy, or offered a text too early.

Send transcript notes to whoever owns store profile updates. Most quality issues trace back to missing FAQ or returns text.

Judge cost against revenue

Use the cost estimator on Pricing to model minutes for your audience size and average call length. Compare that range to attributed revenue from Analytics—not to gross margin alone.

Simple reporting rhythm

Monday: check prior-week answer rate and any spikes in calling cost. Wednesday: read three transcripts from your largest program. Friday: note one store profile fix and one builder tweak to try next week.

Share only metrics your stakeholders understand. Answer rate and attributed orders are easier to act on than a single revenue-to-cost multiple from a partial week.

1. Export mental notes weekly: attempts, answers, attributed orders.
2. If cost rises faster than attributed revenue, narrow audience or shorten calls.
3. If answer rate is low, adjust windows or retry rules before increasing discounts.

Revisit the product analytics page for the full metric glossary if you need language for stakeholder reports—definitions match what you see in the app.

When revenue-to-cost multiple is unavailable because cost is zero, focus on answer rate and connected minutes until live traffic accrues usage.

Export mental benchmarks: what answer rate you need for the program to feel healthy, and what attributed order count makes the next test worthwhile.

When you add a new flow, give it two weeks before comparing to mature campaigns. Early data is noisy and easily misread.

Link metric reviews to concrete actions: profile edits, window changes, or offer steps—not vague “watch it” tasks.

Keep a short log of changes and the week you made them so you can correlate shifts in answer rate or cost with real edits.

When stakeholders ask for ROI proof, share attribution caveats up front. Honest reporting builds more trust than a single heroic week.

End each month by archiving which programs you paused and why—future you will thank present you.