Skip to main content
Send normal HTTPS links from Intercom, email, push, SMS, or any other channel. 
https://app.userjourneys.ai/i/{inviteCode}
https://app.userjourneys.ai/interviews/{inviteCode}
The link contains routing context only. It does not contain conversation tokens, voice agent ids, room ids, or private UserJourneys config.

​
App handling

Configure your app for Universal Links on iOS and App Links on Android for app.userjourneys.ai, then forward incoming URLs to the SDK. For iOS, enable the associated domain: 
applinks:app.userjourneys.ai
For Android, add an HTTPS intent filter for: 
https://app.userjourneys.ai/i/*
https://app.userjourneys.ai/interviews/*
UserJourneys must also authorize your app on the app.userjourneys.ai domain. Provide:
  • Apple Team ID and iOS bundle ID.
  • Android application ID and SHA-256 signing certificate fingerprint.
If Android uses separate debug, staging, and production signing keys, provide the fingerprints for the builds that should open production invite links. 
Linking.getInitialURL().then((url) => {
  if (url != null) void interviews.handleUserJourneysLink(url);
});

Linking.addEventListener("url", (event) => {
  void interviews.handleUserJourneysLink(event.url);
});

​
Fallback behavior

The same link works when the app is not installed. The browser opens the web interview route. When the app is installed and supported, UserJourneys returns a signed WebView launch URL and the SDK opens it in-app. When the app is unsupported or the server chooses not to open in-app, UserJourneys returns an external browser URL and the SDK opens it with React Native Linking.openURL.

​
Intercom

Intercom is a delivery channel in this setup. It can send the HTTPS invite link, but it does not need to know the interview runtime, WebView URL, or voice configuration.

​
Replacing Intercom delivery

If your app uses synced audience prompts, Intercom is not required to get the user into the interview. UserJourneys receives synced audience members from the configured integration, the SDK fetches pending prompts for the current referenceId, and the native prompt opens the in-app WebView when the user accepts. Keep HTTPS invite links for channels where you still want an explicit message: email, push, SMS, Intercom, or support workflows. The same respondent short code preserves attribution in-app and in the browser fallback.