> ## Documentation Index
> Fetch the complete documentation index at: https://docs.go.gbgplc.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Collection of supporting documents
> Invite a customer to a No-code journey that collects supporting documents from them.
This guide shows you how to collect a proof of address document from a single customer and read the details from it. You build a Hosted journey from the Proof of Address Extraction module, invite one customer by email or text message, and then review the extracted details in Investigation. You **don't** write any code or call the API.
By the end of this guide, you can see the address your customer submitted, and whether the GBG Go platform read it successfully.
The **Invite a customer** action is only available for published Hosted journeys. If your journey collects information before it starts, then the action is unavailable. See [When the invite action is unavailable](/docs/go-v2/get-started/quickstart/quickstart-invite-a-customer#when-the-invite-action-is-unavailable).
## Before you begin
Ensure you have the following:
* A GBG Go platform account with a customer admin role. This role lets you review the result in Investigation. If you don't have this role, then contact your GBG account manager.
* The Proof of Address Extraction module enabled in your contract.
* A licence and credentials for the User Invite module set up for your organisation.
* A proof of address document that you can photograph, such as a utility bill or a bank statement.
* An email address or mobile number that you can receive the invite on, so that you can complete the journey as your customer.
## Which module to use
Two modules handle supporting documents, but only one of them works with No-code.
| Module | What it does | Works with No-code |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| **Proof of Address Extraction** | Collects an address document from your customer, and reads the full name, address, and issue date from it. | Yes. Your customer photographs the document on a hosted screen. |
| **Document Attachments** | Collects and stores supporting documents, such as proof of income or a secondary identity document. It stores the files without reading them. | No. The documents are supplied through the API when the journey starts. |
**Document Attachments** takes its documents from the `context.subject.documents` object at journey start, so you must supply the files yourself before your customer begins. An invite carries no data, which means No-code can't provide them. Use Low-code delivery for that module instead. See [Document Attachments](/docs/go-v2/platform/modules/documents/document-attachments) and [Hosted journeys overview](/docs/go-v2/low-code-builder/introduction/hosted-journey).
This guide therefore uses **Proof of Address Extraction**, which collects the document from your customer on a hosted screen.
## Step 1: Create a Hosted journey
1. Click on the **Create a new journey** list.
2. Select **API + hosted (latest)**. This opens the Journey builder, allowing you to design Hosted journey workflows.
3. Click the edit icon on the journey name at the top of the editor.
4. Enter a meaningful name, for example, "Proof of Address - New Customers."
5. Click outside the name field to save it.
## Step 2: Add the Proof of Address Extraction module
You select a variant as part of adding the module.
1. Go to **Browse and add modules** in the right sidebar.
2. Use the search bar to find **Proof of Address Extraction**.
3. Click the module. This opens the module configuration panel, which lists the available variants.
4. Select the **Proof of Address extraction** variant.
5. Click **Add to journey** to insert the module into the flow.
The module extracts the full name, address, and issue date from the document your customer submits. You choose which of these the module requires, and the extraction is successful only when every required selection is complete.
Modules and variants marked with an orange warning icon require activation by the GBG team. If the variant you need is marked, then contact your account manager to enable it for your organisation.
## (Optional) Step 3: Configure the module outcomes
The module arrives pre-configured with the following outcomes, so you can skip this step and go to [Step 4](#step-4-publish-the-journey):
| Outcome | Description |
| -------------------------------------------- | ---------------------------------------------------------------- |
| **Proof Of Address Extraction Successful** | The module read every detail you marked as required. |
| **Proof Of Address Extraction Unsuccessful** | One or more required details couldn't be read from the document. |
| **ERROR** | The extraction couldn't be completed. |
Each outcome is built from one or more rules. A rule tests a capability, which is a single data point the module produces. The module provides the following capabilities:
| Capability | What it tells you |
| -------------------------------------- | ---------------------------------------------- |
| **Proof of Address Extraction Result** | Whether the extraction completed successfully. |
| **Address Is Present** | Whether an address was found on the document. |
By default, the **Proof Of Address Extraction Successful** outcome tests the extraction result alone. Adding **Address Is Present** as a second rule means the outcome also confirms that an address was found.
To add a rule to the **Proof Of Address Extraction Successful** outcome:
1. Click the module inside the Journey builder.
2. Click **Configure outcomes**.
3. Find the **Proof Of Address Extraction Successful** outcome.
4. Click the add icon next to **All Match**.
5. Select **Address Is Present** from the fields list.
6. Set the operator and the value for the rule.
Keep the combinator set to **All Match**, so that the outcome applies only when every rule is true.
In Investigation, you can then see whether each rule returned true or false for that customer.
To learn more about outcomes, see [How to configure module outcomes in Go](/docs/go-v2/guides/product-guides/configure-outcome-decisions).
## Step 4: Publish the journey
Click **Publish to Preview** in the Journey builder. GBG Go displays a confirmation message.
Next, click **Dashboard** to see:
* Environment (Preview)
* Version number
* Resource ID
* Last published
* Actions list
Your journey is now available for testing in the preview environment.
## Step 5: Invite your customer
1. Click the **Actions** list.
2. Click **Invite a customer**. A dialog box appears.
3. Select the options for your use case, and then enter an email address, a mobile number, or both. The dialog box contains the following options:
| Option | Description |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Region** | The region that the journey runs in. Select **EU**, **US**, or **AU**. Your organisation may only be set up in some regions. |
| **Environment** | The environment that the journey runs in. Select **Production** or **Preview**. If you can't select an environment, then the journey isn't published there yet. |
| **Send invite to** | Enter an email address, a mobile number, or both. |
| **Advanced settings** | The link expiry and session behaviour that the invite uses. Expand this to review the current values, which come from the [link settings](/docs/go-v2/platform/link-settings) on the journey. |
The GBG Go platform presets the region and environment based on the journey that you selected. Select **Preview** while you test the journey. Change the region only if your organisation runs journeys in more than one region, because the region controls where your customer's data is processed and stored.
4. Click **Invite**. A message appears at the top right of the screen confirming that the invite started.
An invite is valid for one customer. By default it expires after seven days, and your customer can return to the journey if they close it before they finish. To change either default, see [Link settings](/docs/go-v2/platform/link-settings).
## Step 6: Complete the journey as your customer
Your customer receives a verification link by email or text message.
1. Open the link from the invite.
2. Photograph your proof of address document when the journey asks for it.
3. Submit the document.
Watch this demo to see the journey as your customer experiences it.
The GBG Go platform reads the full name, address, and issue date from the document. It then reaches an outcome based on the details you marked as required.
Capture the document in good light, with all four corners visible and the address clearly readable. A poor image is the most common cause of an unsuccessful extraction.
## Step 7: Review the extraction result
Results are available in Investigation once your customer completes the journey.
1. Click **Investigation** on the left navigation menu. The Investigation dashboard opens.
2. Select the environment that you sent the invite to. If you are testing, then click the **Preview Environment** tab.
3. Select the region that you sent the invite to, using the region list in the top-right corner.
4. Find your customer's session in the list. If the list is long, then click **Add Filter** to search by name or email address.
5. Click the session ID. The session details page opens on the **Processing** tab.
6. Find the Proof of Address Extraction module in the list. The outcome appears on the right of the module name, for example, **Proof Of Address Extraction Successful**.
7. Click the arrow on the module row to expand it. The module shows each rule it evaluated, and whether that rule returned true or false.
8. Click **More details** to drill into the module on its own page, and review the details read from the document.
You have now collected a proof of address document from a customer and reviewed the details read from it.
## Next steps
* Change the decision on a session after your review: [Change decisions](/docs/go-v2/platform/investigate/change-decisions).
* See everything a session records: [View details of a journey session](/docs/go-v2/platform/investigate/view-journey-details).
* Collect supporting documents that don't need reading: [Document Attachments](/docs/go-v2/platform/modules/documents/document-attachments).
* Verify an identity document rather than an address document: [Identity document verification](/docs/go-v2/low-code-builder/no-code/guides/identity-document-verification).
* Invite a customer to a journey built for another verification task: [No-code guides](/docs/go-v2/low-code-builder/no-code/overview#guides).