Conversion types
Eight ways a customer's agent can complete a conversion, one commerce model, and a matrix of where each applies.
A conversion is whatever "yes" means for your business. AGORA's commerce model has eight conversion types. Your packs enable some of them and your merchant settings can narrow them further. The matrix below is normative data shared by every service: must means the conversion works whenever it is enabled for that offering kind, may means it is allowed, and n/a means AGORA answers not_applicable instead of failing, so an agent always gets a clear reply.
Every conversion keeps you as the merchant of record. Payments use your PSP's tokens; AGORA never sees a card number and never confirms a payment itself.
Offering kind × conversion type
| Offering kind | checkout | booking | inquiry | quote | signup | application | subscription | call |
|---|---|---|---|---|---|---|---|---|
product | ● must | ○ may | ● must | ● must | — n_a | — n_a | ○ may | ● must |
service | ○ may | ● must | ● must | ● must | — n_a | — n_a | ○ may | ● must |
plan | ○ may | — n_a | ● must | ○ may | ● must | — n_a | ● must | ● must |
programme | ○ may | ○ may | ● must | ○ may | ● must | ● must | ○ may | ● must |
listing | — n_a | ● must | ● must | ○ may | — n_a | ● must | — n_a | ● must |
membership | ○ may | — n_a | ● must | — n_a | ● must | ○ may | ● must | ● must |
event | ● must | ● must | ● must | ○ may | ○ may | — n_a | — n_a | ● must |
consultation | ○ may | ● must | ● must | ● must | — n_a | — n_a | ○ may | ● must |
other | ○ may | ○ may | ● must | ● must | ○ may | ○ may | ○ may | ● must |
● must work when enabled · ○ may be enabled · — not applicable (answers not_applicable)
The eight conversion types
Source: docs/portal/docs/conversions.md + KIND_CONVERSION_MATRIX (shared/src/generality.ts)