Activity Guide w/ Different Users who are Not Approvers

We have a number of use cases where BEFORE a custom(er) transaction is submitted for approval ONE of the steps in a series of steps is done by a different person. For example

1. Enter Custom(Request) Basic Information - End User 1
2. Enter Custom(Request) Additional Information - End User 1
3. Enter Custom(Request) Accounting Information - Accounting Team User 2
4. Submit for approval
5. (If approved) Do an additional step - Accounting Team User 2

With Fluid Activity Guides it seems like the default is that a single user does all the activity guide steps in sequence.

1. Is there an approach or pattern for splitting the steps between users?