Dinodial Pulse · Drip

What happens after your app
submits a Drip contact?

Your application supplies the contact and callback destination.
Dinodial owns the call and returns one terminal outcome.

✻ Drip · whole journeyone eligible contact
Your application
Dinodial calling system
＋
Contact workflow
choose who should be called
▤
Outcome store
your durable result
◫
Running Drip process
accept and schedule contacts
☎
Call runtime
place and manage the call
↗
Callback delivery
sign and return the outcome
submit contact
schedule
terminal outcome
signed callback
submitted›scheduled›call›returned›saved
The point: Your app supplies intent. Dinodial owns execution. One terminal outcome comes back.
← Back to the Drip guide