This task changes what a customer sees or can buy on a public Selstack journey. This guide focuses on how to use a Lead form before a separate offer, or a current Service or Appointment journey when price is already defined.
Use the current public choices
Create Stack does not show a choice named Lead + payment. Use Service or Appointment when the buyer should provide contact details and then pay, or use Lead form when you must qualify the person before sending a separate offer.
Keep qualification and checkout honest
Ask only for details that affect fit, scope or preparation. If you cannot state a price before reviewing the enquiry, do not present the lead form as an immediate paid checkout.
Build the paid route when the offer is ready
For a defined Service or Appointment, set Free or Fixed amount, select the required fields and choose the correct post-payment outcome. Customer decides is Pro only.
Explain the hand-off
Tell the visitor whether they will receive a quote, a payment link, a booking calendar or a reply, and when. The success message should never imply payment when only a lead was captured.
Troubleshoot the wrong final screen
Review the selected action type, access mode and After success setting. A Lead form and a paid Service are separate public journeys even if they support the same sales process.
Example: Create a Lead Plus Payment Journey
Use a Lead form for a custom renovation enquiry, then send a separate Service offer after review; use Service directly when scope and price are already fixed.
If Create a Lead Plus Payment Journey is not working
If the success screen says payment completed after only a lead submission, correct the action type and success message immediately.
Confirm the result
- Title, media, price, currency, fields and fulfilment details describe the same offer.
- The selected access and delivery options match what happens next.
- The signed-out mobile page shows the complete action without clipping.
- Only a ready, available offer is public.
When to ask Selstack for help
Contact official Selstack support when the saved result, status or resolved identity still conflicts with the intended record after one refresh. Include the business, page, time, safe reference and visible message. Do not include passwords, OTPs, recovery codes, full card details, BVN, NIN or unmasked bank documents.