For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Help CenterOpenAPI SpecStatus
OverviewInquiriesTransactionsRelaysAPI ReferenceChangelog
OverviewInquiriesTransactionsRelaysAPI ReferenceChangelog
  • Overview
    • Inquiries Overview
    • Inquiry Model Lifecycle
    • Inquiry Templates
  • Managing inquiries
    • Creating Inquiries
    • Resuming Inquiries
    • Accessing Inquiry status and data
  • Hosted Flow integration
  • Embedded Flow integration
  • Mobile SDK integration
    • Overview
    • Webview
  • Troubleshooting
    • Troubleshooting Steps
    • Troubleshooting Common Issues
LogoLogo
Help CenterOpenAPI SpecStatus
On this page
  • Statuses
  • Status changes
  • Events
  • Phases
  • What’s the difference between Done & Post-Inquiry?
Overview

Inquiry Model Lifecycle

Was this page helpful?
Previous

Inquiry Templates

Next
Built with

An inquiry wraps a single interaction with one of your end users. This guide explains the various stages and statuses that an inquiry can move through from its creation to conclusion. Together, these stages make up what we call the Inquiry Model Lifecycle. There are four phases in the lifecycle, some of which include multiple statuses.

Statuses

The status of an inquiry defines where an end user is in the inquiry process. Each status change can trigger a configured webhook.

See the diagram below to understand the possible statuses:

inquiry-lifecycle

Status changes

In general, the status of an inquiry can change when:

  1. Your end user proceeds through their inquiry: for example, as they start a verification or complete the flow.
  2. Post-inquiry workflows run and apply business logic to automatically mark an inquiry as “approved”, “declined”, or “needs review”.
  3. Your organization’s members manually change the status of an inquiry.
  4. The inquiry expires.

Events

Every inquiry status change creates an event. You can use these events to trigger other actions, like running a Persona workflow.

The table below summarizes all statuses and their associated events:

PhaseStatusEvent NameStatus Description
Createdcreatedinquiry.createdSet when the inquiry is first created.
Pendingpendinginquiry.startedSet when the end user submits a document or begins a verification.
Donecompletedinquiry.completedSet when end user reaches the Completed screen.
Donefailedinquiry.failedSet when end user reaches the Failed screen.
Doneexpiredinquiry.expiredSet when inquiry exceeds 24hrs, or configured duration, after inquiry created.
Post-Inquiryapprovedinquiry.approvedSet via post-inquiry processes or manual update.
Post-Inquiryneeds reviewinquiry.marked-for-reviewSet via post-inquiry processes or manual update.
Post-Inquirydeclinedinquiry.declinedSet via post-inquiry processes or manual update.

Learn more about inquiry statuses in our Help Center.

Phases

What’s the difference between Done & Post-Inquiry?

inquiry-lifecycle

The “Done” phase describes the inquiry as being “done” from the perspective of the end user. All inquiries will end up at some point in the Done phase (with a status of either Completed, Failed, or Expired).

The “Post-Inquiry” phase is an optional phase that happens after the user is “done”. The provided statuses here—Approved, Needs Review, & Declined—let you mark decisions you might make about the inquiry after the user is done.

When selecting which events, and thus statuses, to configure in your webhooks we strongly recommend configuring both approved & declined as they are the most actionable for your own systems.