Integrations and implementation

This page is for the technical evaluator: exactly how data gets in and out of Fertu, how people sign in, and what implementation asks of your team. Fertu fits alongside the systems you already run. Partner files arrive by SFTP or a secure upload endpoint, forms connect through Typeform, and outreach activity comes out as CSV. Every event is stored in a BigQuery data warehouse that your analyst team can access.

Data in

  • Partner SFTP: Fertu collects your partners’ files directly from their SFTP servers on the schedule you agree with them.

  • Fertu SFTP: partners can drop files on a Fertu SFTP server set up for your program, with a separate named account for each partner. Every login and transfer is logged, files are stored encrypted with dedicated keys, and they’re removed from the transfer area after a retention period you set.

  • Secure upload endpoint: your systems post new records as events happen, authenticated with an environment token, and enrollment and the first outreach step start as soon as the data arrives.

  • Typeform: connect a form in the Fertu Console, and new submissions flow straight into your outreach.

  • Cloud storage and Google Drive: Fertu can collect files from a cloud storage bucket, Google Drive or a Google Sheet.

  • CRM lists: Fertu can pull lists straight from HubSpot or Salesforce.

Fertu works with the file formats your partners already send, adding new ones such as Excel, fixed-width or encrypted files as part of setup. Every file is checked before your campaigns use it, and a file that fails is held back.

Data out

Download outreach activity from the Fertu Console as a CSV: every message with its campaign, step, delivery status, unsubscribe flag, retry reasons and your partner’s own member ID. Each download is logged. Every outreach event is also stored in BigQuery in your dedicated environment, and Fertu can set up an export of call outcomes, such as transfers, voicemails and wrong numbers.

Sign-in

Users sign in to the Fertu Console through a dedicated identity service, and every request must carry a valid access token from that sign-in. Users are added by invitation, so Fertu never issues or sees their passwords. Each workspace accepts only users from your organization, users who work across several workspaces switch between them in one sign-in, and Owner, Admin and Member roles control sensitive actions. Sign-ins, role changes and other account events are logged.

What implementation involves

Fertu creates your environment with a scripted, repeatable setup and manages it as code: dedicated Fertu core infrastructure and its own database, with full isolation on a dedicated database server, or a separate database on a shared, Fertu-managed server. Then Fertu works with your team on:

  • Data mapping: Fertu maps each partner’s file layout to a consistent member record. You’ll want someone who knows your partners’ file layouts.

  • Texting registration: Fertu handles carrier registration for your texting program.

  • Your email domain: Fertu sets up your sending domain with DKIM signing. You’ll want someone who can add DNS records.

  • Call flows: Fertu sets up your call flows. You’ll want whoever approves your call scripts.

Onboarding takes 2 to 8 weeks, depending on scope, custom data feed integrations and EDI enrollment. Support continues after launch. How we work

Works alongside your CRM or email tool

Fertu doesn’t replace your CRM. It pulls lists from HubSpot or Salesforce, reaches provider and practice offices from your CRM’s company lists, and outreach results can be written back to Salesforce or HubSpot through a custom integration built for your program.

Security and compliance

Each customer’s services, data and credentials live on dedicated Fertu core infrastructure. Security and compliance · Platform · Channels

Frequently asked questions

Is there an API?

Yes, for teams that want one. We scope API access with you in discovery.

Do you work with our CRM?

Yes. Fertu can pull lists from HubSpot or Salesforce, and results can be written back through a custom integration built for your program.

Where does our data live?

On dedicated Fertu core infrastructure in Google Cloud, with daily database backups kept in a multi-region US location.

How do we get our data out?

Download outreach activity from the Fertu Console as a CSV, keyed to your partners’ member IDs.