EIGENN.
docsguidesapichangelogpricingsign in
EIGENN.

Tone Profiles and Experiments

Set communication tone, understand delivery analytics, and compare two profiles without a claim beyond what the experiment measures.

Tone Profiles define how eligible payment communications sound. Tone Experiments compare two profiles on real, eligible workflow traffic. They summarize customer assignments and recorded payment conversions.

Neither feature sends a message by itself. A profile or experiment affects communication only in a workflow that has tone turned on. That workflow must have a template, a customer, and the necessary delivery and AI configuration.

Before You Start

  • Connect and test the communication channels that the workflow uses.
  • Create or find a payment-reminder template for a workflow that has tone turned on.
  • Confirm that customer records and invoice context are available to that workflow.
  • Set up the AI provider of the workspace if you expect text transformation.
  • Read the necessary language and the prohibited phrases with qualified legal or compliance owners.

Open Tone Profiles

  1. Open Receivables.
  2. Select Tone Profiles.
  3. Read the performance summary at the top.
  4. Manage profiles under Your Tone Profiles.

Tone Performance Analytics

The page shows:

  • Communications — total tracked communications associated with an explicitly linked tone profile
  • Sent — tracked communications that Eigenn records as sent now
  • Delivered — tracked communications with delivered status
  • Delivery rate — delivered count divided by total tracked communications
  • Deliveries by tone profile — delivered count grouped by linked profile
  • Weekly send volume — sent count grouped by week

These are delivery counts, not payment-conversion or collection-speed metrics. The page now uses all available performance data and a weekly timeline. It does not give a visible date filter.

Analytics attribution follows the profile that you link directly to a communication template. Some communications use a team default without a direct template link. Others get an experiment override at send time. Deliveries by tone profile can attribute these to a different profile than the one that you expect.

Create a Tone Profile

  1. Select Create Profile.
  2. Enter a name that describes the intended use.
  3. Choose a quick-start template or Custom configuration.
  4. Review Tone Settings.
  5. Review Content Rules.
  6. Select Save Profile.
  7. Read the profile.
  8. Use Set Default if you want it as the team fallback.

Eigenn does not make a new profile the default automatically.

Quick-start choices

Quick startInitial style
SaaS FriendlyWarm, customer-centered, and conversational
B2B FirmDirect, professional, and action-oriented
Fintech RegulatedNeutral, formal, and prefilled with compliance-oriented language rules

A quick start prefills the profile. You can continue to edit it before you save.

Tone settings

Choose an Empathetic, Neutral, or Firm preset, then adjust:

  • Formality from casual to formal
  • Empathy from direct to compassionate
  • Urgency from gentle reminder to high priority
  • Reading level from grade 1 through grade 18
  • Brand voice description

Content rules

Set these values:

  • Blocked phrases
  • Necessary disclaimers
  • Optional maximum character length

These rules check transformed content. They are not a legal guarantee. They are not a hard delivery gate for every path. If a transformed body breaks the configured rules, the tone step can fall back to the original template content. The communication can still proceed. Read the original template as carefully as the generated version.

How Eigenn Chooses a Profile

For an eligible communication with tone turned on:

  1. Eigenn prefers a profile that links directly to the template.
  2. If the template has no profile, Eigenn can use the team default.
  3. An applicable customer-segment rule can adjust the profile or its settings.
  4. An active experiment can replace that choice with the A or B profile of the customer.

If no profile is available, Eigenn uses the original template. If the AI provider is unavailable or transformation fails, Eigenn also uses the original template content. It does not block the communication.

This precedence applies to workflow communication that has tone turned on. Recovery steps that you create in Settings → Receivables Controls do not show a template selector. Do not assume that they use tone profiles.

Manage Your Profiles

  • Select the edit icon to change the name, quick-start-derived configuration, tone settings, or content rules.
  • Select Set Default to replace the current team default.
  • Select the delete icon and confirm to permanently remove a profile.

You cannot undo a profile deletion. Templates that link to it fall back to the team default. Eigenn can also remove experiments and segment rules that link to the deleted profile. Choose a replacement. Update the active use. Preserve the experiment results before you delete the profile.

Open Tone Experiments

  1. Open Receivables.
  2. Select Tone Experiments.
  3. Create a new experiment, or select View details on one that exists.

Experiment Lifecycle

Draft

When you create an experiment, Eigenn stores these values:

  • Name
  • Optional description
  • Variant A profile
  • Variant B profile
  • Traffic percentage for variant A, with the rest for B

The two profiles must be different. A new experiment starts as Draft and does not affect communication until you select Start experiment.

Running

Only one tone experiment can run for a team at a time. When you start another, Eigenn returns a conflict until you pause or complete the current experiment.

When Eigenn prepares an eligible communication with customer context:

  1. Eigenn assigns the customer to A or B by the traffic split.
  2. The assignment remains fixed for that customer in that experiment.
  3. The assigned profile becomes the tone choice for eligible messages while the experiment runs.

Traffic split applies to customer assignment, not to a guaranteed message count. Small samples and repeat messages to the same customer can produce an uneven observed split.

Paused

Select Pause. Eigenn then does not select the experiment for new eligible communication. A pause also removes it from the automatic active-experiment lookup for payment outcome records. Eigenn can omit a payment that arrives during the pause from its conversion summary.

Completed

Select Mark completed at the end of the measurement window. Then choose Variant A wins or Variant B wins.

Winner selection is manual. It records the chosen variant. It does not make that profile the team default and does not update templates. Roll out the winner separately in Tone Profiles and any template configuration.

What Experiment Results Mean

The details view shows:

  • Assignment count
  • Conversion count
  • Overall conversion rate
  • Conversion rate for A and B
  • Customer IDs for each variant
  • Created, started, and completed times

A conversion is an assignment with a recorded outcome that has a true converted or paid result. In the supported recovery completion path, a payment from a customer can record that result while the experiment still runs.

The denominator is the assigned customers, not the delivered messages. The page does not show statistical significance, confidence intervals, time-to-payment, or average recovered amount. It also has no guard against a winner decision on a very small sample.

Not every invoice status change records an experiment outcome. Manual paid-state corrections and alternative payment paths can leave an assigned customer without a recorded conversion. Confirm the summary and the source payment records before you interpret the rate.

Experiment Safety and Limits

  • Create at least two profiles before you start.
  • Use profiles that differ in one hypothesis when possible.
  • Keep the experiment active through the payment-observation window if automatic conversion attribution matters.
  • Do not edit or delete variant profiles during an active experiment.
  • Do not treat delivery rate as collection conversion.
  • Do not treat a higher raw conversion rate as conclusive without enough assignments and a suitable review period.
  • Delete permanently removes the experiment and its assignments. The list does not present a separate confirmation dialog.
  • Eigenn permits a 0% or 100% traffic split. That split stops a useful two-sided comparison.

Troubleshoot

A profile saved but messages did not change

Confirm that the message comes from a workflow with tone turned on and a template. Confirm that the template-specific or default profile is available. Then confirm that you set up the AI provider. On a failure, Eigenn uses the original template.

Tone analytics show no profile data

The analytics include only the communications with templates that reference a tone profile directly. The profile groups can omit a default-only or experiment-overridden use.

An experiment has no assignments

Confirm that it shows Running. Confirm that no other experiment runs. Confirm that Eigenn prepares eligible template-based workflow communications with customer context. An experiment or an Auto-chase policy alone does not create assignments.

Assignments exist but conversions remain zero

Confirm that the assigned customers paid through a path that records an experiment outcome while the experiment ran. A paid invoice status alone is not enough evidence that Eigenn updated the experiment summary.

The observed traffic split is uneven

Assignment is random and sticky by customer. Small samples, repeat communications, and customer-level rather than message-level assignment can produce an uneven split.

The profile that won did not become default

Winner selection only records the experiment decision. Open Tone Profiles and select Set Default. Then update any template-specific profile separately.

Related Pages

  • Run a Receivables Tone Experiment
  • Receivables
  • Receivables Controls
  • Invoice Collection Workflow
  • Invoices

Teams and Organizations

Understand workspace boundaries, member roles, invitations, how to switch teams, and owner-managed identity organizations.

Transaction Categories and Rules

Build a reporting taxonomy and automate repeat transaction decisions with deterministic rules.

On this page

Before You StartOpen Tone ProfilesTone Performance AnalyticsCreate a Tone ProfileQuick-start choicesTone settingsContent rulesHow Eigenn Chooses a ProfileManage Your ProfilesOpen Tone ExperimentsExperiment LifecycleDraftRunningPausedCompletedWhat Experiment Results MeanExperiment Safety and LimitsTroubleshootA profile saved but messages did not changeTone analytics show no profile dataAn experiment has no assignmentsAssignments exist but conversions remain zeroThe observed traffic split is unevenThe profile that won did not become defaultRelated Pages

Eigenn docs

current product

Overview
Overview
OverviewAccount PreferencesAssistant AutomationAssistant Command CenterBank ConnectionsBilling and UsageBudgets and ForecastCommand CenterCustomer LifecycleCustomer RecordsCustomersDeveloper PlatformDocument Processing and ExtractionDocument VaultFinancial Analytics and ReportsFinancial OverviewInvoice InsightsInvoice ProductsInvoicesMarketplace IntegrationsNotifications and BrandingOnboarding and SupportOverviewReceivablesReceivables AnalyticsReceivables ControlsSecurity and AccessSettings OverviewStress TestsTeams and OrganizationsTone Profiles and ExperimentsTransaction Categories and RulesTransactionsWeekly Finance RitualWorkflow ExecutionsWorkflow PausesWorkflowsWorkspace Inbox and Approvals
OverviewBuild and Review a ForecastBuild Your First WorkflowConfigure Assistant OperationsConfigure Notifications and BrandingConfigure Receivables ControlsConnect Transaction RecordsCreate and Manage CustomersCreate and Send InvoicesDeveloper API SetupFirst Cash ReviewInvoice Collection WorkflowMaintain Transaction RulesManage Security and BillingManage Team AccessManage the Invoice LifecycleMCP WorkflowsMonitor and Recover WorkflowsOrganize and Share DocumentsProcess Inbox ItemsReconcile and Categorize TransactionsReview a Customer Finance RecordRun a Finance Operating ReviewRun a Receivables Tone ExperimentRun a Runway Stress TestRun Your First Command Center ReviewSet Up a WorkspaceTroubleshoot Account AccessWebhook DeliveryWeekly CFO Review
OverviewIntegrationsMCPSDKsWebhooks
OverviewAuthenticationBank Accounts APICustomers APIErrorsForecasts and Stress Tests APIInvoice Payments APIInvoices APIPaginationRate LimitsRemote Tracker API StatusTracker Categories APITracker Entries and Timers APITracker Projects APITransactions APIWebhooks API StatusWorkflows API Status
Overview
Overview