Banking CRM
In a bank, the branch, the loans team and operations each touch the same customer separately; the promise made stays in that unit's own notebook. When a file is held up, finding out who asked for which document means calling the customer one more time.
An application is a record with stage and missing-document fields, and which document is awaited from whom sits on the card. In Rapitek CRM an objection enters the queue as its own case record.
- Follow loan and product applications through their stages, write the missing document into a field on the record, and send the reminder from there
- Plan visits to corporate customers in the portfolio as tasks, and enter the visit note from the field with the mobile application
- Open customer objections and complaints as case records, put them in the queue and drop them to their owner through the assignment rule you defined during setup
- Segment consented communication lists and run SMS and WhatsApp notifications from a shared inbox
| Application File | An application is a record with stage and missing-document fields; which document is awaited from whom sits on the card. |
|---|---|
| Portfolio Visit | A visit is a task; the portfolio manager, the account and the date are in its fields, the visit note is written on the same record, and the location is confirmed in the mobile application. |
| Objection and Case | A customer objection is a case record; it enters the queue, reaches its owner through the assignment rule defined during setup, and at closing the survey is tied to the same record. |
| Communication Consent | Consent status is a field on the customer card; the campaign list is filtered by that field, and a record without consent does not enter the list. |
In banking, the reason a file is late is not the decision but a missing document. The paperwork requested from the customer is mentioned on the phone, repeated by e-mail, and who asked for what stays in personal correspondence; when the portfolio manager changes, the customer has to send the same document a second time, while where the delay occurred is never visible on the institution's side.
In Rapitek CRM an application is a record with stages and missing-document fields; who asked for what and when sits on the same card, and the reminder that goes to the customer is produced from that field as well. Objections and complaints enter the queue as their own case record, reach their owner through the assignment rule defined during setup, and at closing the satisfaction survey is tied to the same record. We build the connection to the core banking system; there is no out-of-the-box module, the connection is built specifically for the project over the REST API and webhooks.
The scope of the plans and the items priced separately are written on the pricing page.
