Great! So what I would envision is that you could extend your current decision diamond section where it figures out that the contact already has purchased a ticket, and removes the “1 ticket” tag and applies that “2 tickets” or “3 tickets” etc. tags.
The logical path that comes to my mind would be to have the sequence after the decision diamond where it removes the “1 ticket” tag and applies the “2 tickets” tag ALSO send an email to the contact requesting that they click a link and fill out the contact information for the person they purchased a ticket for. The form that they fill out will be a goal in the campaign, and if they do fill out the form it will send them into another set of decision diamonds and sequences where the “2 tickets” tag will be removed and the “1 ticket” tag will be applied.
A tricky part is figuring out how the purchasing contact is linked to the one that is created when the form is filled out. Since it’s a new contact being created presumably if they’re entering a different name/email, I don’t think it will trigger anything in the campaign for the purchasing contact when the form is filled out. It’s fairly simple if you’re using the API, because the form itself should get the contact ID of the purchaser when the link is clicked to fill out the form. I’m not 100% sure if there’s a way to do it with out-of-the box Infusionsoft, but it’s probably worth a shot before pulling in the API.
I know that’s a technical answer with a lot of unanswered questions, but this is a pretty involved campaign and there’s a lot of branching so a lot of designs are possible and as with all design there are tradeoffs. I’m happy to keep helping though, and the more details you give about the project the more I can try to offer insight on the tradeoffs and what I would recommend!
