DobroDesk update: mobile SDK and order workflows inside chat
We have shipped Mobile SDK 0.2.0 and expanded what customers can do inside a DobroDesk conversation.
Customers can work through configured order and booking flows in chat. They provide the required details, review the proposed action and receive a result from the connected service. Follow-up actions, such as checking a request or changing an appointment, stay in the same conversation when the connected workflow supports them.
For a booking, that means choosing a service, date and time, reviewing the exact details and confirming before the action runs. Available slots and results come from the connected provider. When a person needs to take over, the teammate has the conversation history and collected details.
Mobile SDK 0.2.0 brings this conversation model into iOS and Android apps, with Flutter, React Native, Capacitor and NativeScript support. App teams can add support where their customers already are.
AI uses approved knowledge and shows the sources behind a draft. Human review is the default. Automatic replies and actions run only within the workspace rules. Sensitive or uncertain cases stay with a person.
We have also improved conversation loading and switching in the Inbox.
The Support plan is EUR 19/month for 300 accepted conversations, unlimited teammates and three active published automations. Extra usage is EUR 24 per started 1,000 additional accepted conversations. A public Help Center is a separate EUR 19/site/month add-on.
Demo:
SDK guides: https://dobrodesk.com/developers
For teams bringing order or booking workflows into chat, where do you most often need a person to take over? I would like to hear which steps should stay self-service and which need a human decision.




Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.