Selstack is a platform for creators and businesses to build a public selling page, share individual offers, accept supported payments and bookings, and manage the resulting orders and customer details. A “Stack” is a selling page. This guide explains the relevant workflow and the seller’s responsibilities; payment methods, account requirements and some features depend on the business configuration and plan.
The Contacts area brings together people captured through lead and payment journeys, so follow-up does not depend on searching old conversations.
Find a contact
- Open Contacts from the sidebar.
- Use search or the available filters to narrow the list.
- Open the contact to review the details and source context available to your workspace.
- Confirm that the record belongs to the correct person before updating or acting on it.
Use link questions carefully
Good contact data begins with the form. Ask only for details needed to qualify, deliver or follow up. Use specific field labels so the customer knows what to enter. Do not request passwords, payment credentials or unrelated sensitive information.
Follow up with context
Refer to the offer or question that brought the person in. A relevant message is more useful than a generic promotion. If you intend to send marketing email, use the consent and preference process appropriate to your business and audience.
Keep information accurate
Correct obvious errors only when you can verify the change. Avoid creating duplicate records for the same conversation. If a person asks not to receive marketing, apply that preference in the systems you use.
Access control: customer information should be visible only to people who need it for their role. Never export or share contacts simply because a tool makes it possible.
Connect an enquiry to the customer relationship
Selstack brings customer details and relevant activity into the business workspace so a seller can follow up with context. A contact may come from an enquiry, a form submission or another supported customer action. Those origins are not interchangeable. Someone asking about a service has not necessarily bought it, and someone claiming a resource has not necessarily agreed to every future marketing message. Use the record to understand what the person actually did and what response the business has a legitimate reason to provide.
Give a form one clear purpose
Decide what should happen after a visitor submits the form. A useful form might collect the details needed to answer a product enquiry, assess a service request or deliver a promised resource. Explain that purpose on the page and make the final action understandable. Do not describe a general enquiry as a confirmed order or a place in a booked appointment. If payment is part of a later step, explain when it will be requested and what must happen before the service or product is reserved.
Choose questions that change the next action
Each question should help the business deliver the promised response. A service enquiry might need the type of project, its timing and a suitable contact route. A product question might need an item name or order reference. Keep required fields limited to information needed at that stage. Extra questions can reduce completion and create more personal information to manage. Avoid collecting passwords, security codes, full payment-card details or unrelated identity information in an ordinary lead form.
Review the submission experience
Open the form’s public URL while signed out and check it on a phone. Read the title, explanation, labels and completion message as if you had not seen the editor. Submit a safe test using clearly identified test information and confirm that the result reaches the intended business and record. If the form promises a resource or follow-up, inspect that hand-off too. A successful-looking message on screen should match a useful result in the workspace, not merely reassure the visitor that a button was clicked.
Read the source before following up
Open the contact or lead record and review its context before sending a message. Establish which offer or form created the interaction and what the person asked for. A follow-up that refers to the actual enquiry is more useful than a generic introduction that makes the customer repeat everything. If the record is incomplete, ask one focused question. Keep any manual notes factual and relevant, and distinguish information supplied by the customer from assumptions made by the team.
Organise contacts around useful decisions
A mailing list or segment should help the business choose a relevant audience. A group interested in a particular resource can receive a related, permitted update; it should not automatically include every past customer. Review the source and membership of a list before using it for a campaign. Avoid building so many overlapping groups that the team cannot explain why a person belongs to each one. Simple, understandable organisation is easier to maintain and reduces the chance of sending the wrong message to the wrong audience.
Keep consent separate from necessary service messages
Information needed to answer an enquiry or fulfil an order has a different purpose from optional marketing. Explain an invitation to join a mailing list separately and respect the person’s choice. Do not disguise ongoing promotional consent as a requirement to receive an unrelated answer. If a person unsubscribes or asks to stop receiving marketing, use the supported suppression process and review any external list copies the business controls. Moving the same address to another list should not be used to evade that choice.
Maintain accurate, limited customer information
Correct ordinary errors when they are identified and avoid creating several conflicting records for the same interaction. Limit access to people who need the information for their role. Before exporting data, establish the business purpose, destination and responsibility for protecting the copy. Keep customer details out of public notes or screenshots shared for unrelated reasons. A cleaner record improves service because the next authorised person can understand the customer’s situation without searching across several messages and spreadsheets.
Measure follow-up by the outcome it should support
Review the number of useful enquiries, response times and the outcomes relevant to the original form. A submission is not automatically a qualified buyer or a paid order. If many people misunderstand what they will receive, improve the form’s explanation before increasing promotion. If good enquiries are not followed up, assign a clear owner and review point. Selstack connects the form and customer context; the business’s response determines whether that information becomes helpful service, a suitable sale or an unnecessary interruption.
Review Selstack pricing for current plans and online payment fees. For related tasks, visit the Help Centre. If the recorded result remains unclear, contact support with the relevant safe reference.
