Plain
Plain built an autonomous support agent, and has now built the controls to trust it.
A side-by-side editorial comparison of DoneDone and Twilio — release velocity, themes, recent moves, and the top alternatives to consider.
Small, customer-requested fixes all summer — then the first automation engine.
DoneDone ships in a tight loop with users: reorderable checklist items, tags in CSV exports, collapsible Kanban columns, more board sort fields, and activity feeds that hide status noise by default. Several entries name the customer request that prompted them. On August 7 the pattern broke with Workflow Automations, the first release in this window that adds behavior rather than tidying existing behavior.
Twilio is retiring its old serverless runtime while pushing consent and deliverability control into APIs.
The changelog reads as a platform in consolidation. Functions Classic is being retired with an automatic migration, the REST API certificate chain is being rotated, and older SendGrid behaviours are being trimmed. Alongside that, the messaging and email surfaces keep gaining programmatic control that used to be manual or impossible: bulk WhatsApp templating with cross-channel fallback, dedicated IPs with managed warm-up for Twilio Email, and a Consent Management API that can now clear network-level toll-free opt-outs.
DoneDone ships in a tight loop with users: reorderable checklist items, tags in CSV exports, collapsible Kanban columns, more board sort fields, and activity feeds that hide status noise by default. Several entries name the customer request that prompted them. On August 7 the pattern broke with Workflow Automations, the first release in this window that adds behavior rather than tidying existing behavior.
The through-line is reducing friction in a board people already live in, and Workflow Automations extends that logic one step: instead of a cleaner view of manual work, the status change itself now sets due dates and attaches checklist templates. Checklist Templates got management improvements in July and are the object of the new automation in August, which suggests templates are being built up as the standardization primitive the product organizes around.
The automation surface starts narrow — two actions on one trigger — so the obvious next steps are more triggers than status change and more actions such as assignment or notification. The customer-request cadence in these entries suggests those will arrive in the same incremental way.
The changelog reads as a platform in consolidation. Functions Classic is being retired with an automatic migration, the REST API certificate chain is being rotated, and older SendGrid behaviours are being trimmed. Alongside that, the messaging and email surfaces keep gaining programmatic control that used to be manual or impossible: bulk WhatsApp templating with cross-channel fallback, dedicated IPs with managed warm-up for Twilio Email, and a Consent Management API that can now clear network-level toll-free opt-outs.
Twilio is collapsing parallel generations of the same product - two Functions runtimes, SendGrid-era email versus Twilio Email - onto one platform, and simultaneously turning operational levers into API surface. Compliance is where that shows most clearly: consent, branded calling, and registration feedback are all becoming things you configure programmatically rather than things you file a ticket about. The deprecation notices and the certificate rotation share an audience of customers running old integrations, and Twilio is spending its changelog budget telling them what breaks and when.
Expect the migration cadence to continue through the September and October Functions cutover with follow-up notices on edge cases, and expect more of the compliance surface - the new TFV and A2P error codes already scheduled for September 15 - to land as API-readable signals rather than console-only state.
Other Support products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either DoneDone or Twilio.
Plain built an autonomous support agent, and has now built the controls to trust it.
Sleekplan rebuilt itself around AI triage, then put the feedback board inside ChatGPT.
Comm100 publishes steadily about AI support — none of it is Comm100 shipping anything.
respond.io is layering an agent-authoring copilot and consumption billing on top of its omnichannel inbox.
Hatz sells through MSPs, and its roadmap has started to serve the partner more than the end user
A teaser-only content feed making one argument: AI in the contact center fails on knowledge, not models.
See all DoneDone alternatives → · See all Twilio alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Twilio is currently shipping more aggressively (velocity 8.8 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Twilio is currently shipping more aggressively (velocity 8.8 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Support products to evaluate alongside.
Top DoneDone alternatives in Support are ranked by recent ship velocity. Browse the "DoneDone alternatives" section above for the current picks, or visit /alternatives/donedone for the full list with editorial commentary on each.
Top Twilio alternatives in Support are ranked by recent ship velocity. Browse the "Twilio alternatives" section above for the current picks, or visit /alternatives/twilio for the full list with editorial commentary on each.