Skip to content

Glossary

Key terms used throughout Fynex. These definitions are consistent with the product and documentation.

Core Concepts

TermDefinition
AI agentA conversational agent that contacts debtors via WhatsApp, voice, email or SMS, follows strategy rules, logs interactions and promises, and escalates when criteria are met.

Accounts & Contacts

TermDefinition
AccountA debt record in your portfolio. Contains the amount owed, due date, status, and associated contact.
ContactThe person associated with an account — name, email, phone, WhatsApp number.
ReferenceYour internal identifier for the account (invoice number, case ID, etc.).
PortfolioThe collection of all accounts in your organization.

Statuses

StatusApplies toMeaning
NewAccountRecently imported, not yet contacted.
Pending ContactAccountScheduled for first outreach.
Auto ManagementAccountBeing managed by AI agents.
Active ConversationAccountAgent is mid-conversation with debtor.
Promise ActiveAccount / PromiseDebtor committed to pay, within due date.
Promise OverdueAccount / PromisePayment promise past due.
PaidAccountDebt resolved.
EscalatedAccountRequires human intervention.
PausedAccountTemporarily removed from automated contacts.

Strategy & Campaigns

TermDefinition
StrategyA set of rules defining how agents contact debtors: channels, sequence, frequency, escalation criteria.
Action SequenceThe ordered list of contact steps in a strategy (e.g., email day 1, SMS day 3, call day 7).
CampaignAn operational grouping of accounts under one strategy and time period. The execution engine enforces campaign status (draft/active/paused/completed) and date range. Active campaigns can be enqueued manually or automatically.
EscalationWhen an account is moved to the human queue because criteria are met (max attempts, days without response) or the agent requests it.
Escalation CriteriaConditions that trigger human review: max attempts reached or days without response.

Channels

TermDefinition
ChannelA communication method: email, SMS, WhatsApp, or voice.
Voice opening modeFor AI voice calls, whether the callee speaks first (agent waits for pickup, then follows the prompt script) or the agent speaks first (immediate greeting TTS). Resolved from manual call choice → strategy + step → organization Voice default → product default.
Credential ModeWhether Fynex's credentials ("platform") or your own ("self-managed") are used for a provider.
DispatchThe act of sending a message or initiating a call to a debtor.
TemplateA predefined message with variable placeholders, used by agents when contacting debtors.

Interactions & Promises

TermDefinition
InteractionA single contact event (message sent, call made) with its channel, result, and timestamp.
PromiseA debtor's commitment to pay a specific amount by a specific date.
ModalityWhether the promise covers the total debt or a partial amount.
Opt-outWhen a debtor requests not to be contacted. All future dispatch to that contact is blocked.
DispositionThe detailed outcome classification of a voice call (e.g., promise to pay, callback scheduled, refusal, wrong number).
Contact ResultWhether the intended person was reached on a call (connected, no answer, voicemail, wrong number, disconnected, etc.).
CallbackA return call scheduled at the debtor's request. The strategy step is paused until the callback fires.
Channel PreferenceThe debtor's preferred communication channel, captured during calls and used to route future contacts.
Phone RotationAutomatic selection of the best phone number for a call, considering previous results (wrong numbers, disconnected numbers) and alternate numbers.

Execution & Payments

TermDefinition
Execution QueueThe work queue where the engine places pending dispatch actions. Items progress through pending → processing → completed/failed/skipped.
PaymentA recorded money transfer from a debtor. Automatically reduces the account balance and can fulfill a promise.
DisputeA formal objection raised by a debtor. While open, it is tracked separately with status, reason, and resolution notes.
NotificationAn in-app alert for important events: overdue promises, escalations, channel errors, batch failures.

Integration & API

TermDefinition
API KeyA secret token used for machine-to-machine authentication with the Fynex REST API. Created in Settings > Integrations.
WebhookAn HTTP callback that Fynex sends to your server when specific events occur (e.g. account created, promise broken).
External IDA unique identifier from your source system, stored on accounts and contacts to enable cross-system mapping.
Source SystemA label identifying which external system an account or contact was imported from (e.g. "core_banking", "crm").
ScopeA permission level assigned to an API key, controlling which resources it can read or write.
UpsertCreate-or-update operation: if a record with the same external_id exists, update it; otherwise create a new one.
HMAC SignatureA cryptographic hash used to verify that webhook payloads were sent by Fynex and not tampered with.
Import JobAn async operation that processes a batch of accounts via the API, tracking progress and errors.

Language

TermDefinition
LocaleA regional language variant (e.g. es-AR, pt-BR, en-US). Determines dialect, compliance rules, voice, and templates for outbound content.
Language cascadeThe priority order Fynex uses to pick the language for any outbound interaction: manual override → contact language → organization locale → country default → es.
Supported languagesSpanish (es — Argentina, Mexico, Colombia), Portuguese (pt — Brazil), and English (en — US). Set the organization locale in Settings; set per-contact language in Portfolio import.

Compliance

TermDefinition
Frequency LimitsMaximum number of contacts per day and week, configured in Settings.
Allowed HoursThe daily time window during which contacts are permitted.
Audit LogImmutable record of all system events, actions, and configuration changes.
Dispatch ValidationPre-send checks (opt-out, frequency, hours, paused status) that must pass before any contact.