How to send sms/email with journey link(s) to multiple people

Good morning!

Use case:
During sign in process, I need to send sms/email to different people for their signature.

How to send different journey links so that when customer clicks the link, I would need to take them to the different web flow.


In order to send individualized Journey Links, you need to start a new Journey for each person you want to send a new Journey Link to. From your description, it sounds like you have a primary application, and then, as an end user goes through the flow of that primary application, there’s a point in which you will want to fire of a secondary application, such that it sends out it’s own Journey Links to several other people?

If that’s the case, you’ll probably want to trigger you secondary application via an App API, which the primarily application can send HTTP requests to in order to trigger the secondary application.

Does that help? If not, can you go into some more detail on your use case?

1 Like

Thanks Chandra!

If it’s simple signature, I would agree. But my use case is that, as a Primary applicant, I completed changes and signature and then I to send request to co-owner to complete their signature. When co-owner access the link, they should see all other changes that were done by primary applicant.
It’s huge data and how can I send this data to other journey(if it is new application)?
Once they completed the signature, how can I update the primary application with co-owner signature ?

Instead of going with another Airkit application, can we do something in the existing app itself ?

Thank you again for your response on this one.

The challenge with doing it in one application is that if the primary applicant clicks on the session link that is sent to the co-owner, the would see the same experience, meaning you can’t seperate the two. That’s why using seperate apps that are triggered via App APIs is probably the better way to go about it. With the app APIs you can pass data to the new journey through the request body of the POST request.

Then once they complete the journey on the co-owners app, you can then have an app API set up on the original app that does a lookup against the session id and runs an event to continue the journey.

so in short:

  1. Primary signature App make a request to: →
  2. App API on secondary signature app
  3. On completed send an API request back to primary signature app to an App API endpoint set up on primary signature app
  4. App API configuration needs to do a lookup against journey using a session identifier
1 Like

@Narendra Here’s a video on how i would do this:

1 Like

Awesome ! Thanks a lot Ismaen. This is what exactly I am looking for.

You guys made my day.

1 Like