Operator by Fibric
Field Dispatch
A managed early-access pattern for matching supported field signals to a reviewed route and dispatch proposal.
View details
← Marketplace
ConnectorControl & actuation
Twilio
Calls and texts the right person when an operator decides to act, throttled and deduplicated on Fibric's side.
Ask how Twilio fits what you run.
Answers are based on this listing. For anything it can't answer, our team can.
For anything this page can't answer, talk to us.
About
The Twilio connector sends SMS and places voice calls through Twilio's API when an operator's decision needs a human: the on-call engineer, the site manager, the crew nearest the fault. Messages are composed from the event that triggered them, so the text names the equipment, the site, and what the operator proposes, and delivery status flows back as events an operator can act on if a page goes unanswered.
Throttling and deduplication are Fibric-side discipline, not something the API does for you: one incident produces one page per recipient per window, a re-fired rule collapses into the message already sent, and rate limits per tenant keep a runaway loop from becoming a flood. The connector is managed early access: built and maintained by Fibric, wired with a Fibric deployment engineer through the early-access program, with sends starting propose-only.
Highlights
- Calls and texts on decision
- Throttled + deduplicated
- Writes use idempotency keys and single-flight controls to suppress duplicate effects on retry
- Provisioned with a deployment engineer through the early-access program
- Kind
- Connector
- Category
- Control & actuation
- Publisher
- Fibric
- Availability
- Early access
- Delivery
- Managed by Fibric; nothing to install
- Data direction
- Reads and writes
- Pricing
- Early access
- Sold by
- Fibric
- Support
- Developed and supported by Fibric
- Tags
- sms, voice, dispatch, comms
Authentication
Authenticates to the Twilio API with your account SID and auth token, scoped to the messaging service and numbers you assign.
What it reads
- Delivery status per message and call: queued, delivered, failed, no-answer
- Inbound replies, so an acknowledgment can close a page
- Per-tenant send rates against configured throttle limits
What it can do
- Send an SMS to a named recipient, deduplicated per incident and window
- Place a voice call with a spoken summary of the event
- Escalate to the next contact when a page goes unacknowledged
How it works
1
Sense
Delivery status per message and call: queued, delivered, failed, no-answer.
2
Reason
Operators reason over this connector's signals next to the rest of your stack, so decisions are grounded in the same records you run on.
3
Act
Target capability: Send an SMS to a named recipient, deduplicated per incident and window. Actual authority, duplicate controls, and recovery depend on the validated deployment and downstream system.
Pricing
Managed early access
This listing is informational and not self-serve. A deployment review must validate the connector, credentials, action boundary, recovery path, support, and contractual pricing before use.
- Deployment engineer
- Wires and verifies the integration with you during onboarding
- Managed validation
- Review maturity, authority, supported records, and deployment boundaries before go-live
- Execution records
- Supported reads, proposals, policy decisions, and reported outcomes kept for review
- Support from the builders
- Developed, run, and supported directly by Fibric
Requirements
- A Twilio account with a provisioned number or messaging service
- A contact list or on-call schedule for recipients
Your deployment engineer verifies each line with you during onboarding.
Support and resources
Supported by the people who built it
This connector is developed, run, and supported by the same Fibric team. Support starts during onboarding with a named deployment engineer and doesn't hand you off afterward.
Works with
Listings this is designed to pair with. Each listing has its own live or managed early-access state.
Operator by Fibric
Shift Coverage
A managed early-access pattern for spotting a coverage gap and proposing qualified cover for human confirmation.
View details
Operator by Fibric
Predictive Maintenance
A managed early-access pattern for reviewing supported telemetry and proposing a maintenance work order before a suspected fault worsens.
View details
Sensing & telemetry connector
LoRaWAN Network
Pulls low-power wide-area sensors into Fibric: door, leak, temperature, and tank-level readings across a whole campus, on one feed.
View details
Support & comms connector
Slack
Posts the proposed action, waits for the human confirm, then executes, all inside a channel that keeps the record.
View details
This connector is developed, published, and supported by Fibric. It integrates with Twilio through published APIs. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy
Bring Twilio into your early-access deployment
Early access means a deployment engineer wires this with you, and it runs propose-only until you approve live actions.