Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/Engage/Sign/RemoteSig.htm

## Capturing Remote Signatures for BRC Samples During Engage Meetings

Remote signature capture allows for BRC sampling during Engage meetings. End users can sample BRCs via the call report and capture a signature while hosting the Engage meeting, extending the user’s ability to provide BRC samples to HCPs without needing a face-to-face meeting. End users can also capture remote signatures for BRC samples from child calls created from a unique activity group call during an Engage meeting. Remote signature capture grants end users more flexibility when planning, scheduling, and executing Engage meetings when a BRC sample is requested. Additionally, HCPs can easily provide signatures without needing to access a link to navigate to the signature page.

**Who can use this feature?**

* Business Admin Users - Browser
* End Users - iPad
* [Capture remote signatures for sampling during Engage meetings](#Using)
* [Review remote signatures](#Reviewing)
* HCPs - Browser
* [Provide a remote signature](#Providing)
* Users require an Engage license

### Considerations for Remote Signature Capture for Sampling During Engage Meetings

* Supported only when hosting an active remote meeting from the iPad
* Samples can only be of product type BRC. If the user selects a Sample other than BRC, an error message displays when trying to capture the signature.
* Remote signature capture is only supported for person calls and [unique activity](../../../Call_Reporting_2/Executing/Activities/UniqueActivities.htm) child calls. Unique Activity parent calls or other business account calls are not supported.
* HCPs joining via the Web Client must use Chrome, Firefox, Safari, or Edge Chromium
* HCPS are able to receive signature requests on Web Client, iOS, and Android HCP apps

See [Capturing Electronic Signatures for Sampling](../../../CallSampling/SignatureCapture/SigCap.htm) for more information about capturing signatures.

### Configuring Signature Capture for Sampling During Engage Meetings for

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)All Users](#)

To configure remote signature capture for sampling in Engage meetings:

1. Ensure the following are complete:
   * [Creating Sample Requests (BRCs)](../../../CallSampling/Disbursements/CreateBRC.htm)
   * [Configuring Engage Meeting](../ConfiguringEngage/ConfigureEngageMeeting.htm)
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the permission set for the appropriate user profile.
4. Navigate to **Objects**.
5. Grant all users Edit field permission to the **signature\_captured\_remotely\_\_v** field on the following objects:
   * call2\_\_v
   * sample\_order\_transaction\_\_v
6. Grant Edit field permission to the **remote\_signature\_attendee\_name\_\_v** field on the call2\_\_v object. With Edit field permission, the call stamps with the name of the attendee entered when joining the remote meeting.

Additionally, to configure remote signature capture for sampling in a unique activity call:

1. Ensure [Unique Activities](../../../Call_Reporting_2/Executing/Activities/UniqueActivities.htm) are configured.
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the permission set for the appropriate user profile.
4. Navigate to **Objects > Calls**.
5. Grant View access to the **general\_call\_section\_\_v** object control for the appropriate object type.
6. Navigate to **Admin > Configuration > Objects > Call > Layouts**.
7. Select the appropriate layout.
8. Add the **General Call** section to the layout for the appropriate object type with the Enable Remote Meeting checkbox selected.

### Capturing Remote Signatures for Sampling During Engage Meetings as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

To capture a remote signature, the end user hosting the Engage meeting must do the following:

1. Select the **Signature** action from the call report.
2. Use the Signature Setup page and select **Remote** as the Signature Method. If the marketing banner is configured for the in-person signature page, it is available for the host to select.

   The marketing banner must be less than 1 MB in size. See [Displaying a Marketing Banner](../../../CallSampling/CaptSigforSampling/SigBanner.htm) for information.
3. Select the disclaimer text language and indicate if the HCP wants to receive a receipt for the BRC request.
   This step is only available if [Displaying Country-Specific Disclaimers](../../../CallSampling/SignatureCapture/CountrySpecific.htm) is enabled.

   ![](../../../../Resources/Images/Multichannel/Engage/EngageeMeeting/RemoteSignatureCapture.png)
4. Select **Request Signature**.
5. Select the appropriate attendee. This step only displays if multiple attendees are using the same Engage meeting ID as the selected account.

   ![](../../../../Resources/Images/Multichannel/Engage/EngageeMeeting/RemoteSignatureCapture2.png)

A Requesting modal with a spinner displays to the meeting host until the HCP sends their signature back to the host.

![](../../../../Resources/Images/Activities/CallReporting/CallReportSampling/RemoteSignatures 2.png)

### Providing a Remote Signature as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)HCPs](#)

To capture a signature, HCPs need to do the following after the signature page launches on their screen:

1. Review the request details including the HCP’s license information, requested BRC samples, shipping address, and disclaimer.
2. Sign in the Signature box.
3. Select **Accept** to send the signature. The Signature page becomes locked and the signature is sent to the meeting host for review.

A confirmation message displays to the meeting host indicating receipt of the HCP’s signature.

### Reviewing Remote Signatures as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

The meeting host can review and accept the signature. When the host selects Accept, all fields are stamped, consistent with an in-person signature capture, and the signature\_captured\_remotely\_\_v field sets to True on the following objects:

* call2\_\_v
* sample\_order\_transaction\_\_v

The following Signature Location fields are not stamped:

* signature\_location\_latitude\_\_v
* signature\_location\_longitude\_\_v

### Connectivity/Timing Scenarios

Losing connectivity from the meeting during the remote signature request process:

* If either the host or HCP loses connection after the host receives a signature from the HCP on their device, the host can still accept the signature
* If the host’s connectivity is lost before receipt of the HCP’s signature, the host needs to re-initiate the remote signature request

### Related Topics

[Capturing Remote Signatures for BRC Samples Using Share Link (Sign Now)](RemoteSigSampling.htm)

[Capturing Asynchronous Remote Signatures for BRC Samples Using Share Link (Sign Later)](RemoteSigAsync.htm)

[Capturing Asynchronous Remote Signatures for BRC Samples Using Share Link (Sign Later)](RemoteSigAsync.htm)
