Status
The status helps track which processing step a donation record is currently in. A status can be set manually, through quality checks and workflow conditions, as well as through call center or cancellation imports.
If multiple workflow conditions apply simultaneously, the following priority applies:
failed > cancelled > stopped > held > call > conditionally-approved > approved > live
The same status values can—if provided for in the campaign setup—also be used as charity and agency statuses.
| No. | Status | Meaning |
| 0 | none | The record has no workflow status. This status is mainly used in campaigns without an activated workflow module. In such campaigns, usually only held is additionally used. |
| 1 | awaiting-validation | The record has been uploaded and is waiting for quality checks and workflow conditions to be evaluated. This status usually exists only briefly. |
| 2 | held | A problem has been detected with the record. It is held back and should be manually reviewed. This status can be used in all campaigns, even without an activated workflow module. |
| 3 | call | The donating person should be called. Therefore, the record is intended for export to a call center. Note: If the record contains no phone number, the call status cannot be maintained. If it is nevertheless set, the system automatically changes the status to approved. |
| 4 | approved | The record has been fully reviewed and can be exported to the organization. |
| 5 | conditionally-approved | The record is valid, billable, and can be exported to the organization, but does not fully meet all requirements. Examples include a downgrade during a phone call or an unmet contractual requirement, such as a mandatory welcome call. |
| 6 | failed | The record was canceled or definitively rejected before export to the organization, for example after too many failed payment attempts or a manual cancellation. |
| 7 | live | The record was successfully exported to the organization and is active. |
| 8 | cancelled | The record was canceled after export to the organization, for example after too many failed payment attempts or a manual cancellation. |
| 9 | stopped | The record has already been transmitted to the organization, but the donation is no longer active and no further payments can be made. |
Status Reasons
A status reason explains why a record received its current status. It can be set in different ways:
- through automated data validations and quality checks,
- through workflow conditions,
- manually in the detail view of a workflow-enabled campaign,
- during a manual cancellation,
- through a call center import.
Each status reason is only allowed for certain statuses. In the detail view, the associated code is displayed in addition to the name, for example Data change - other (FCO-3-999). If multiple workflow conditions are triggered, the status comment shows which status reasons and codes were responsible.
Status reasons marked with * can also be used as values for welcome_call_outcome.
General and Frequently Used Status Reasons
| Code | Status Reason | Applicable For |
FCO-0-000 | - * | Call; default value if no call result was set |
FCO-99-000 | Multiple Status Reasons | Call or multiple simultaneously triggered reasons |
FCO-99-001 | Incomplete data set | Approved, Conditionally Approved, and Call |
Status Reasons for Approved and Conditionally Approved
| Code | Status Reason |
FCO-1-001 | Long term confirmed * |
FCO-1-002 | Converted One-off * |
FCO-1-003 | Form sent * |
FCO-2-001 | No time for call attempt * |
FCO-2-002 | Wrong number * |
FCO-2-003 | Not responded * |
FCO-2-004 | Temporarily unavailable under this number * |
FCO-2-005 | Donor voice mail requesting no call * |
FCO-2-006 | Voice mail left by agent * |
FCO-2-007 | Language problem * |
FCO-2-008 | Refused * |
FCO-2-009 | Unwell * |
FCO-2-010 | Deaf * |
Status Reasons for Held
| Code | Status Reason |
FCO-2-011 | Number of different person * |
FCO-3-001 | Data change - lower donation amount * |
FCO-3-002 | Data change - interval * |
FCO-3-999 | Data change - other * |
FVO-10-001 | Address Validation failed |
FVO-10-002 | Quality Check failed |
FVO-10-003 | Donor Feedback comment |
FVO-10-004 | Status conflict |
FVO-10-005 | Blacklisted |
FVO-10-006 | Unknown Status Import |
Status Reasons for Failed and Cancelled
| Code | Status Reason |
FVO-1-001 | Felt pressured * |
FVO-1-002 | Can't afford * |
FVO-1-003 | Spouse objected * |
FVO-1-004 | Changed mind * |
FVO-1-005 | Doesn't remember signing up * |
FVO-1-006 | Told one-off * |
FVO-1-007 | No longer * |
FVO-1-008 | Cancel without reason * |
FVO-1-009 | Told just petition (leads) * |
FVO-1-010 | Gone away * |
FVO-1-011 | Considered vulnerable * |
FVO-1-012 | Downgrade under minimum * |
FVO-1-013 | Deceased * |
FVO-1-014 | Mystery shopper * |
FVO-1-015 | Test donation * |
FVO-1-016 | Made redundant * |
FVO-1-017 | Unemployed * |
FVO-1-018 | Start date outside range * |
FVO-2-001 | Potential fraud |
FVO-2-002 | Duplicate donor * |
FVO-2-003 | Friends and family |
FVO-2-004 | Same account / different details |
FVO-2-005 | Account name differs |
FVO-3-001 | Number missing (lead) |
FVO-3-002 | Email missing |
FVO-3-003 | Opt-in missing |
FVO-3-004 | Self checkout unsubscribed (leads) |
FVO-4-001 | Max amount attempts |
FVO-4-002 | Invalid bank details |
FVO-4-003 | Account closed |
FVO-4-004 | Changing banks |
FVO-4-005 | Direct debits not permissible on this account |
FVO-4-006 | DD refund claimed |
FVO-4-007 | No instruction |
FVO-4-008 | Instruction cancelled |
FVO-4-009 | Instruction expired |
FVO-4-010 | Payer reference is not unique |
FVO-4-011 | Transaction code/user status incompatible |
FVO-10-011 | No quality check |
FVO-10-012 | No receipt |
FVO-10-013 | Told confirmation call |
FCO-99-002 | Duplicate donor - addendum |
Workflows
Workflow conditions check data fields based on defined rules. Values can be checked, among other things, for greater than, less than, equals, or not equal. Workflows can generally only be created by the Formunauts support team.
The checks can be performed at different times:
- when uploading a donation record, after the quality check has been successfully completed,
- again after receiving donor feedback.
If multiple workflow conditions apply, the status with the higher priority is set:
failed > cancelled > stopped > held > call > conditionally-approved > approved > live
Examples of Workflow Conditions
- Set the record to
heldif donor feedback contains a comment (donor feedback comment is not equal to “empty”). - Set the record to
heldif the age is under 25 years (age is less than 25; less than or equal is also possible). - Set the record to
heldif the address country does not match the specified country (country is not equal to the defined value). - Set the record to
conditionally-approvedif the annual contribution is over 500 (annual contribution is greater than 500).
Comments
0 comments
Please sign in to leave a comment.