Customer conversations next to customer money
Buying a billing system and a CRM separately means two customer records, two licence fees and an integration project to keep them agreeing with each other. OpenBRM ships with a CRM module so the quote, the ticket and the invoice refer to the same account.
What the module covers
- Quotes — priced from the same product catalogue that will bill the order
- Support tickets raised against a customer account and its subscriptions
- Bulk SMS and email notification to segments of your customer base
- Automatic reminders — renewals, anniversaries, prepaid refill prompts
- Configurable notification templates tied to billing events
Notifications driven by billing events
The most useful customer messages are the ones the billing system already knows to send: invoice issued, payment failed, plan about to renew, prepaid balance running low, collections step reached. Because notifications are configured alongside the billing and collections processes, these fire from the event itself rather than from a scheduled job guessing at state.
When you already have a CRM
Plenty of operators run Salesforce, vTiger or SugarCRM and are not replacing it. OpenBRM integrates with vTiger and SugarCRM directly, and exposes its data over SOAP and REST for anything else. The built-in CRM is there so that smaller providers do not have to buy a second system on day one — not to force a migration on those who have one.
CRM and gateway integrations · Notification configuration · Collections process