Bank credit applications straight from the deal

The credit application lived outside the CRM: the manager re-entered client and vehicle data by hand, and the bank's decision was not visible in the deal — it was chased by phone. From the deal alone, there was no telling where the application stood or why it was declined.

The exchange runs through a financial broker whose actual callback format differed from the spec; the bank has its own status dictionary, and credit products have amount and term limits. Once the contract is approved, an application can no longer be submitted.

• A "Credit applications" smart process with 21 result fields and role-based permissions: a manager sees their own applications, a head of department sees their department, an admin sees everything
• Submission to the broker from the deal card: a draft, checks of required fields and product limits, a block on submitting after contract approval, and double-click protection
• Callback intake: key-based authorization, idempotency by eventId, tolerant body parsing — callbacks had silently failed to save for 5 days because of a mismatch with the spec; found and fixed
• A bank status dictionary — 28 business statuses and 16 technical ones; a final decision creates an activity for the manager and is written to the deal timeline
• An SMS to the client with a link to the bank questionnaire under a "one application — one SMS" rule, with delivery-report intake
• An exchange log across 6 directions, a "Submit application" business-process robot, and a morning watchdog for applications with no events for over 3 days