When completing a Work Order in the field, the Technician needs to capture twoSignatures to...

The correct configuration is Signature Types and Signature Blocks on the Service Report Template. For multiple signatures, define the relevant Signature Types and place a separate Signature Block for each type on the Service Report Template. The technician can then collect the required approvals when the report is generated in Field Service Mobile.

When comparing Salesforce Mobile with Field Service Mobile, the latter should be treated as an operational field-work client rather than a generic CRM client. Its offline capabilities, appointment-centric experience, signature/report functions, geolocation controls, and technician-specific actions are the features that should drive the configuration decision.

The alternatives address different parts of the Field Service model. Separate Service Reports, custom fields, or a custom Flow are unnecessary when the native Service Report signature model already supports multiple signature roles.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Mobility — Service Reports; Signature Types; Signature Blocks.