Setup test

Reply.io Setup Test: Saved Sequence, Previews and Fallback Syntax

Setup test completed · New User Plan trial

Published 2026-10-21 · Report updated 2026-10-26 · Tested by Jimmy Dwyer

Jimmy Dwyer · Publisher and responsible editor
Jimmy runs StackVouch and is responsible for this article's conclusions, disclosures and corrections. About Jimmy · LinkedIn

We may earn a commission if you buy through links on this page. Affiliate disclosure.

No paid sponsorship. Reply.io did not review this article before publication.

Read the Reply.io buying review →

The result at a glance

Observed resultBuying implication
Unsent email + task sequence saved and reopened with the configured content and displayed waits retainedThe tested draft configuration persisted before launch; this does not verify timed execution
Two synthetic previews rendered first names; complete company rendered and missing company used the documented fallbackThe bounded preview cases passed; send-time substitution was not tested
The prefixed company fallback advertised by the native picker reproduced a compilation errorSupport later acknowledged incorrect rejection of valid Contact.-prefixed fallbacks and said a fix is in progress; our unprefixed Company previews passed, but a live fix is unverified
Company-complete self-profile enrichment attempt returned an insufficient-credit errorAn access result, not a no-match; support later clarified that rewards require a separate guided onboarding, and no credit award was tested
October 21 export access was absent or disabled in the inspected People, Reports and Stats surfacesNo job or file was obtained; support later said contact export is trial-restricted and free of credit charges on all paid plans; report conditions were not re-tested
Final sequence remained New/unlaunched with two synthetic contacts, unassigned senders and no outbound actionDelivery, reply handling, stop conditions and account safety remain outside the test

The findings apply only to the dated account workflow and stated conditions. See the full limits section before generalizing them.

On this page

Purpose and test conditions

Could Reply.io retain an unsent sequence, render basic personalization for controlled fixtures and expose a usable evaluation path without connecting a sender? Jimmy Dwyer used an ordinary self-service trial on October 20–21, 2026. No vendor special access, sponsorship or advance review.

The initial editor phase began without contacts. Jimmy then added two synthetic contacts for preview and his own profile input for a bounded enrichment check. Only the synthetic records were enrolled into the unlaunched sequence. No mailbox, LinkedIn account, CRM, API key or extension was connected; no sequence was launched and no outreach message, invitation, test email or purchase was made. A later factual support inquiry is recorded in the revision history.

For buying context, read our Reply.io review. This report records the workflow evidence and its limits.

Saved sequence and results

The sequence was named StackVouch Trial - UNSENT - 2026-10-20. Reply allowed contact addition to be skipped. We saved an explicitly unsent email plus a To Do task. The email body used first-name personalization and, after the fallback investigation described below, an unprefixed company fallback.

Reloading retained the sequence name, email subject/body, the one-day wait before the email, the task description and the displayed two-day task wait. That establishes configuration persistence, not execution timing.

Reply saved sequence reopened with the editorial email and task retained
Saved sequence content remained after reload; no send was performed.

Two synthetic personalization previews

We created two synthetic records with no real email, phone or LinkedIn URL. One was linked to a synthetic company; the second deliberately had no company. Both records survived reload and were kept in a named fixture list.

With the final saved body, the complete fixture rendered its synthetic first name and company. The missing-company fixture rendered its synthetic first name and the literal fallback your company.

Reply preview with a complete synthetic company
Complete synthetic fixture: first name and company rendered in preview.
Reply preview with the missing-company fallback
Missing-company synthetic fixture: the configured fallback rendered in preview.

These two previews verify only the saved preview behavior. They do not establish send-time substitution, deliverability or arbitrary fallback syntax.

Fallback syntax difference

The editor’s Advanced picker advertised {{Contact.Company | 'your company'}}. In this account, two entered-text attempts with that prefixed form produced a compilation error and disabled Save. We later inserted the prefixed entry directly from the native picker; the compilation error reproduced.

Reply compilation error after native picker fallback insertion
The prefixed fallback advertised by the picker reproduced the compilation error in this draft.

The vendor templates-and-variables documentation instead showed {{Company | 'your company'}} without the prefix. Entering that form allowed saving and produced the two preview results above. Support later recommended this same unprefixed form as a workaround; see the October 22 vendor clarification. Later support replies supplied October 23 acknowledge incorrect editor rejection of valid Contact.-prefixed fallbacks and say a fix is in progress. The deployment of that fix has not been confirmed or re-tested.

Jimmy’s own profile and the credit gate

Jimmy used his own profile input for a bounded enrichment check. Before a company was linked, one Find email addresses action showed that a request had started, but no terminal result was established. After Jimmy supplied his actual StackVouch company/domain and linked it to his record, a second attempt returned an explicit insufficient-credit error.

The account displayed zero Reply credits, and no purchase link was followed. No real email or phone was obtained. Reply support later explained that the 50 trial credits are earned through eligible onboarding actions rather than granted upfront. Later replies clarified that the manually built sequence does not count toward the separate guided onboarding. Support says its generated My first sequence can award the first 20 credits after adding contacts and reviewing steps. No guided flow, credit award or new enrichment result was recorded. The denominator is one real target with two attempts under different input conditions, not two sampled people or two completed searches. This is an access result, not evidence of a contact-data miss.

Final unlaunched boundary

The final sequence contained the same email and task plus the two synthetic contacts. There were zero sending accounts and Launch remained disabled. The real self-profile was not enrolled.

Reply final sequence with two synthetic contacts, no sender and launch disabled
Final test boundary: two synthetic contacts, no sending account and no launch.

Reply and meeting handling defaults were inspected, but no reply or meeting event was generated. The settled summary displayed AI response generation enabled and an approximate four-day duration; no AI setting was changed and no response was generated.

October 21 CSV access re-test

We rechecked export access without performing credit-dependent operations. Global selected-contact and formal sequence contact menus did not expose an export command in the inspected surfaces. The synthetic-company contact menu also lacked it. Reports/Emails and the formal sequence Stats page exposed disabled Export buttons.

Reply formal sequence People view with no export command exposed
The formal sequence People view contained the synthetic fixtures; no export command was exposed in the inspected controls.
Reply sequence Stats page with Export disabled
Sequence Stats exposed Export, but the control was disabled.

No CSV job was submitted, no file was downloaded and no export-credit charge or credit error was observed. The controls did not identify a cause during the October 21 inspection. In the later support response, Reply said contact CSV export is unavailable during trial; email reports have separate access conditions. Those report conditions were not re-tested. A later reply said contact CSV export is available on all paid plans without consuming credits. That is a vendor clarification, not an observed paid export or charge measurement; trial export access remains separate from the enrichment-credit gate.

Trial and pricing context

Plans & Billing identified the subscription as New User Plan and displayed a 14-day trial ending November 3, 2026, with $0 as the next invoice total. The account also displayed 0/300 active contacts, 1/1 users, 0/2 mailboxes, 0/0 Reply credits, 0/0 email validation and 0/0 LinkedIn accounts. These are account-specific displays, not universal trial entitlements.

The October 20 account chooser showed Email Volume at $59 monthly or $49 as the displayed monthly equivalent with annual billing at the 1,000-active-contact setting. Multichannel showed $99/user monthly or $89/user with annual billing. We did not enter checkout or verify taxes, renewal or cancellation terms.

On October 21 Jimmy re-opened Plans & Billing and both billing selectors without subscribing. The entry prices remained the same. Mailbox and credit wording still differed between surfaces; the selected screenshots below preserve the exact labels. The welcome message mentioned 50 trial search credits, while this account showed 0/0. Support later explained that the trial credits are earned through eligible onboarding actions rather than granted upfront. No balance change or eligibility check was recorded. The zero balance is not proof that credits were spent or enrichment returned no match.

View Plans & Billing and dated price selectors
Plans & Billing, October 21, 2026: New User Plan trial, zero connected mailboxes and 0/0 Reply credits. These are account-specific displays.
Plans & Billing, October 21, 2026: New User Plan trial, zero connected mailboxes and 0/0 Reply credits. These are account-specific displays.
Email Volume, October 21, 2026: Monthly selected, 1,000 active contacts, $59/month and 25 mailbox-connection seats shown.
Email Volume, October 21, 2026: Monthly selected, 1,000 active contacts, $59/month and 25 mailbox-connection seats shown.
Email Volume, October 21, 2026: Annually selected, 1,000 active contacts, $49 monthly equivalent; annual commitment, not monthly cancellation.
Email Volume, October 21, 2026: Annually selected, 1,000 active contacts, $49 monthly equivalent; annual commitment, not monthly cancellation.
Multichannel, October 21, 2026: Monthly selected, $99/user/month, five mailboxes and 50 AI personalization credits shown.
Multichannel, October 21, 2026: Monthly selected, $99/user/month, five mailboxes and 50 AI personalization credits shown.
Multichannel, October 21, 2026: Annually selected, $89/user/month equivalent, ten mailboxes and 50 Reply credits/month shown.
Multichannel, October 21, 2026: Annually selected, $89/user/month equivalent, ten mailboxes and 50 Reply credits/month shown.

Vendor clarification supplied October 22, 2026

Jimmy supplied a written Reply support response to the three factual questions on October 22. The statements below are attributed vendor clarification; no product re-test or advance article review took place.

Trial credits

Support said the 50 Reply credits are earned through eligible onboarding actions rather than granted upfront, and 0/0 may remain until credits are earned. Support offered to check eligibility and credit history if the required actions had been completed. That initial reply did not identify the required flow. Later replies, recorded below, explain the separate guided sequence; no credit award or successful lookup was observed.

Variable syntax

Support recommended {{Company | 'your company'}} as a workaround. This matches the form already saved and rendered in our complete-company and missing-company synthetic previews. The editor-recommended {{Contact.Company | 'your company'}} had produced a compilation error in the tested draft. That initial reply offered escalation if the workaround failed. Later replies confirm it was forwarded and acknowledge an editor issue under repair; no deployed fix has been confirmed.

Contact CSV versus email reports

Support said contact CSV export is unavailable during the trial. Email report exports follow different rules: a loading report or no matching filtered data may disable export; if the menu opens but its final button is disabled, an export type must be selected. In Reports > Emails, Trends CSV also needs a comparison date range. Support said a remaining disabled state after meeting the requirements would need further investigation.

We have not re-tested these conditions, completed a contact export or email-report export, inspected a resulting file, earned onboarding credits or measured a new charge. The earlier sequence Stats observation remains dated evidence; we do not assume the Reports > Emails explanation establishes its cause. The later reply below clarifies paid contact-export entitlement and no-credit charging; the original inspection still produced no file.

Further vendor clarification supplied October 23, 2026

Jimmy supplied three later support replies after the initial explanation. The order matters: support first queried why completed-looking actions had not earned credits, then clarified that the required onboarding is a separate guided sequence. This is vendor clarification; the original test conditions and dates remain unchanged.

A manually built sequence does not count toward guided onboarding

Support said clicking Start on the Sequences onboarding card creates a separate My first sequence. Adding contacts and reviewing the steps there earns the first 20 credits. Our manually built draft is separate and does not advance that progress. In its earlier reply, support identified connecting an email account and launching as the remaining actions toward 50 credits in total.

We did not click Start, create that guided sequence, earn credits, connect a sender or launch. The first-20-credit path is support’s explanation, not an observed award. A zero balance after the manually built draft does not establish exhausted credits, a contact-data miss or a general reward defect.

Paid contact CSV export does not consume credits, according to support

Support said contact CSV export is available on all paid plans, is unavailable during the trial and is free to use without consuming credits. This clarifies a subscription gate rather than an export-credit requirement. We have not tested a paid plan, generated a contact CSV or verified a charge. Email reports remain a separate export type; their loading, filter, type-selection and comparison-date conditions were not re-tested.

Support acknowledged the prefixed-fallback editor issue

Support confirmed that fallback variables with the Contact. prefix are currently rejected by the editor even though they are correct, and said the team is fixing the issue. It recommended the equivalent unprefixed forms {{Company | 'your company'}} and {{Title | 'sales leader'}}.

Our two earlier synthetic previews already passed with the Company form. We have not tested the Title example, send-time substitution or the corrected editor. No fix-live notification was supplied. The finding can now be described as a vendor-acknowledged editor issue with a demonstrated Company-preview workaround, rather than only an unexplained difference between two examples.

These statements come from Jimmy’s supplied support email transcripts. Original send timestamps were not provided. The linked mail-image attachments were not inspected or used as independent test evidence. No new product operation or advance article review occurred.

Limits and interpretation

  • One authenticated trial account, two synthetic preview fixtures and Jimmy’s own profile input.
  • No outbound send, sender connection, delivery event, reply event, meeting event, call, SMS or LinkedIn automation.
  • No independent email/phone accuracy or coverage benchmark.
  • The prefixed-fallback result is a reproducible editor observation in this draft, not a universal product defect claim.
  • The self-profile result is a credit gate, not a no-match result.
  • CSV access was checked only on the stated October 21 surfaces; no file was generated or inspected.
  • Pricing observations are dated account/public displays, not a verified checkout total.

Re-test history

Date What changed
October 20, 2026 Created and reopened the unsent sequence; recorded editor defaults, pricing/account surfaces and the initial zero-contact boundary.
October 20, 2026 — preview and self-profile checks Added two synthetic preview fixtures, reopened the named list, reproduced the native-picker fallback error and recorded the self-profile enrichment credit gate. The sequence remained unlaunched.
October 21, 2026 Rechecked CSV access without credit-dependent actions. Export was absent or disabled in the inspected views; no CSV job or file resulted. The formal sequence independently remained New with activation off and 0/100 sending counter.
October 21, 2026 — editorial correction Named Jimmy as the tester and owner of the self-profile input; added literal fallback expressions, dated billing/price captures, the standard author and commission disclosure, and the Setup test label. No connected sending or performance test was added.
October 21, 2026 — vendor clarification requested Sent three factual questions to Reply support: the promised 50 trial credits versus 0/0 allocation, the two fallback expressions, and contact/report export access rules. Reply’s in-app assistant opened an official support conversation. No substantive support answer had been received when this revision was prepared; causes remain unresolved. This request is not advance vendor review or approval of the article.
October 22, 2026 — vendor clarification supplied Jimmy supplied Reply support’s written explanation of onboarding-earned trial credits, the documented company-fallback workaround, and separate contact/report export rules. Added attributed clarification without changing the October 20–21 observations or last-tested date. No new send, credit allocation, enrichment or export result; picker root cause and report-export behavior remain unverified.
October 23, 2026 — further vendor clarification supplied Added the separate guided onboarding and first-20-credit explanation; recorded that support says paid contact CSV export is free of credit charges; recorded vendor acknowledgement of the Contact.-prefix editor issue under repair. No new guided flow, credit award, sender connection, launch, paid export or deployed-fix test. Earlier observations remain dated October 20–21.