Skip to main content

​
Choose your workflow

Origination and collections use different intake workflows. Choose one before creating customers or scheduling calls.

​
Origination: new leads and returning borrowers

  1. Start with the Origination overview.
  2. Send a whole list with Batch Enrollment, or send one application to Enroll an Application with scheduleMode: "enroll", the enabled taskType, and an Idempotency-Key. Each enrolled application creates or reuses the customer and saves its cadence.
  3. For a single application, save the returned enrollment receipt. For a batch, save the jobId from the 202 Accepted response and poll its Location URL for per-row results and enrollment receipts. Then monitor schedules and calls.
There is no separate customer-create prerequisite or scheduled-calls request. Use the complete examples for new leads, returning borrowers, and one-off outreach.

​
Collections: configured loan-based boarding

  1. Create the customer.
  2. Create the loan. For accounts configured for loan-based collections boarding, this creates the collections schedule.
  3. Monitor the resulting schedule and completed calls.
See Upcoming API Changes for changes to the Create Customer contract. These changes do not alter origination enrollment.

​
Monitor Call Results

After calls are executed, you have two options to access the call data:

​
Option A: Fetch Calls via API

Use List All Calls to export company-wide call history with cursor pagination and optional filters. For an individual call or customer, use these routes:

Get Call by ID

Retrieve a specific call’s details

Get Calls by Customer

Retrieve all calls for a customer
Example Request:

​
Option B: Receive Calls via Webhook

Call-result delivery requires a separately configured webhook. Enrollment does not enable one or configure notes and flags in your LMS. Confirm the delivery format and destination with your account manager before building a receiver.

Call Webhook

Receive automatic notifications when calls complete

​
Understanding Call Data

The response depends on the endpoint. Call detail exposes transcript, recordingUrl, and timestamp, which may be null; company-wide call history uses a different schema. The current call-detail response does not expose flags or summaries. Scheduled-call responses describe scheduling state; their postProcessingFlags field is currently null. Do not assume a webhook uses the API response’s field names or timestamps. Validate notes, summaries, and flag delivery separately from enrollment.

Get Scheduled Calls

View scheduled calls and their scheduling status

​
Managing Scheduled Calls

You can also manage scheduled calls after creation:

Cancel Single Call

Cancel a specific scheduled call

Cancel All Calls

Cancel pending scheduled calls for a customer

​
Best Practices

  1. Track Saved Schedules: Use the enrollment receipt’s Location to inspect the scheduled call. A saved schedule does not mean a call has completed.
  2. Use Your Own Customer IDs: When creating customers, use the id field to pass your internal customer ID. This ensures you can easily reference customers between your system and Finosu.
  3. Confirm Result Delivery: Agree on webhook configuration and the schema before relying on flags or summaries in your LMS.
  4. Validate Stop Workflows: Before retiring a funded/stop upload, verify that its replacement stops the cadence, not just individual pending calls. See Origination stop workflows.