This task establishes the foundation for a usable Selstack workspace. This guide focuses on how to validate the customer journey without exposing sensitive information or creating fulfilment confusion.
Why this matters
This task helps you validate the customer journey without exposing sensitive information or creating fulfilment confusion. Complete it inside the business you intend to manage; the name in the workspace header tells you which business will receive the change.
Find the right starting point
Use the main navigation and match the page heading to the task. Dashboard is a summary, Stack manages public offers, Contacts holds customer and lead context, Payments contains orders, Wallet shows business balances, and Settings controls account or public identity.
Complete one clear change
Read the existing value before editing it. Enter current, truthful information and use the page’s primary save, publish or continue action once. If Selstack shows a field error, correct that field rather than opening another copy of the form.
Check the result
Look for the saved state, updated value or confirmation message. When the task affects a public link, open the real URL while signed out and inspect it on a phone. When it affects a record, reopen that record and match its name or reference.
If something looks wrong
Confirm the active business, refresh the relevant page once and compare the saved value with the public or downstream result. Do not create duplicate links or payment attempts to make an uncertain status disappear.
Example: Run a Safe Test of a New Offer
Use realistic non-sensitive details and stop before an unintended live charge unless an approved test-payment method is available.
If Run a Safe Test of a New Offer is not working
A successful preview is not proof of checkout, digital delivery or wallet credit; verify each state separately.
Confirm the result
- The workspace header shows the intended business.
- The page displays the expected saved or published state.
- Any public result is readable while signed out on a narrow screen.
- No duplicate link or action was created while checking the result.
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.