The tool is integrated with a number of (primarily mobile) tools, and the idea is simple. Take a photo on your smartphone, upload it to Yabber, and do something with it. If used in our 'Formly' forms, and if you're sending a photo of a licence, we'll populate form fields with OCRed values, such as names and licence number (this basic function applies to any matching text field in *any* OCR response type, not just licences). If sending via the CRM endpoint, an image (and optional PDF) is sent to your CRM (attached to a user or as a general note/task), and if using the social action, the images is schedule for social. In total there's nearly a dozen endpoints that all have their own associated action.
In the couple of years we've made the OCR component of the API available it's already almost a redundant feature, particularly with the indroduction of our BeNet Agentic AI... but it's still useful in company with our suite of APIs (on Github) that'll create and then send self-hosted online applications to various CRM systems.
The attached photos show the most basic flow, although the screen differs based on the type of photo or image.
Interestingly, the system has seen almost exclusive usage from our 1000+ auto/equipment clients that use it for trade-in photos or similar, and our Property clients use it heavily to upload real-time photos and video into their various CRM tools when Camera isn't supported.
While I continue to argue that OCR and AI-enabled upload tools should be considered baseline features in modern CRMs, our decision to publish open implementations ensures that businesses of all sizes can adopt, adapt, and extend the system. This openness not only accelerates adoption but also positions the API as a foundation upon which broader digital strategies can be built.
