How long does the Slack integration take to ship?
Our standard window is thirty days from signed scope to live Slack adapter in production, plus a one-week monitored stabilization phase. For Champaign, Illinois, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
What happens if Slack changes their API after we go live?
Our SRE team monitors Slack change announcements and rolls compatibility updates inside our maintenance retainer. If a breaking change ships, we own the migration; you don't pay extra to stay current and you don't field calls from the vendor.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Champaign, Illinois. After go-live, the Slack adapter runs on a flat monthly run-rate sized to message volume — no per-API-call gotchas, no per-seat surcharges, and a one-page exit clause.
Does it work with our existing Slack licenses?
Yes — the adapter rides on top of your existing Slack subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.
Can the Slack adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your Slack tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
Is this a packaged Slack connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.