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.
Turn available hours, scope, revisions, support load, fees and a sustainable margin into a repeatable operating process that produces a service price and volume the business can fulfil without hidden overtime.
A repeatable operating routine should connect Selstack orders and customer context to fulfilment, support, finance and team responsibilities.
Define the decision and its owner
Turn the topic into an operating decision rather than a vague aspiration. Document available hours, scope, revisions, support load, fees and a sustainable margin. Name the person responsible, the Selstack record they should check and the status or event that starts the work.
Write the normal path in plain language
Describe the few steps that should happen for a typical order, contact, support request or financial review. Use the authenticated Selstack record as the shared reference. A short process that the team follows is more useful than a large document nobody can apply.
Add controls where errors are expensive
Require a second review for changes involving money, access, customer data or irreversible fulfilment. Separate preparation from approval where possible. Do not share administrator credentials or move sensitive decisions into private messages that leave no reliable history.
Plan the exception path
Write what happens when information conflicts, a payment is pending, stock is unavailable, a deadline moves or a customer disputes the outcome. State who can decide, what evidence is safe to collect and when official support or a specialist must be involved.
Review evidence on a useful rhythm
Use paid orders, fulfilment time, customer questions, refunds, support load and available balances according to the decision. Compare the current period with the same definitions, not a changing collection of vanity metrics. Assign actions and review dates, not only observations.
Keep the process proportional
The target is a service price and volume the business can fulfil without hidden overtime. Simplify steps that add no control and strengthen steps that protect customers or funds. Avoid selling unlimited access or discounting below the cost of reliable delivery. The process should remain usable when the business is busy or a different team member takes over.
A practical example
A five-hour service should include preparation, revisions, fees and support time when setting a sustainable fixed price.
When the result is unexpected
If demand exceeds capacity, adjust availability or pause promotion rather than promising unlimited access.
Connect the service promise to the booking
Selstack supports service offers and time-based bookings, but they solve different customer needs. A service page can describe a project or piece of work without asking the customer to choose a time immediately. An appointment connects a defined service to availability and a booking process. A service menu can present several bookable services and applicable deposits. Choose the structure that reflects how the business actually delivers the work. The page should help a customer understand whether they are buying a finished outcome, reserving time or requesting a conversation about a larger project.
Define what is included and what is separate
Write the service in terms a customer can recognise: the duration, deliverables, preparation, number of participants and the follow-up they should expect. A consultation might include one conversation and a short written summary; a design service might include specific files and a stated revision process. These are examples of promises the business must define, not universal Selstack package rules. Explain what falls outside the price. If the work needs a proposal after the first conversation, say so before the customer books rather than suggesting the session includes the entire project.
Set realistic capacity and timing
Review the time required to prepare, deliver and follow up, not only the visible appointment length. Availability should reflect the hours the business can genuinely offer. Check the appointment’s time zone and how it appears to a visitor in another location. Avoid copying a date from an informal message without confirming the zone. If a service is delivered remotely, explain how joining instructions will reach the customer. If it is in person, provide the practical location information and any relevant access arrangements through the supported booking process.
Explain the amount and payment expectation
Make the service price and currency clear. An appointment paid in full is different from a service that takes a deposit or requires a later quote. Describe the selected arrangement accurately and review the customer-facing summary before publication. Do not use a free enquiry form while telling the customer that submitting it automatically confirms a paid booking. Likewise, a failed or incomplete payment attempt should not be treated as proof that the customer has secured a session. Use the status shown on the relevant booking and payment records when deciding what is confirmed.
Ask questions that help you prepare
Collect the information required to deliver the service well. A useful question might establish the topic the customer wants to discuss, a project deadline or a relevant preference. Avoid asking for an entire history when a short preparation note will do. Do not request account passwords, one-time codes or full payment credentials in a booking form. If sensitive professional information is necessary for the service, use an appropriate process and explain its purpose. A clearer intake process can improve the session without turning a straightforward booking into an unnecessarily long questionnaire.
Test confirmation from the customer’s side
Inspect the public booking page while signed out and on a mobile screen. Check the service name, duration, currency, available dates and final action. Use an authorised test to review the booking confirmation and the information the customer can retrieve afterwards. Confirm that a booking is attached to the intended business and service. If you use a calendar or meeting integration, verify the connected account and the resulting event rather than assuming that selecting an integration proves the hand-off works. Keep a practical support route available for missing joining instructions.
Prepare a dependable follow-up
After the service, deliver any promised notes, files or next steps through the agreed channel. Keep the follow-up consistent with the offer: a summary should not suddenly become an unannounced ongoing subscription, and a project discussion should not be reported as a completed project. Explain a proposed additional service as a separate choice. For a customer who needs to change a booking, refer to the terms and available controls rather than improvising a different rule in every conversation. Clear records make it easier for another authorised team member to help.
Improve the offer from real sessions
Review questions customers ask before booking, preparation that repeatedly takes longer than expected, and follow-up tasks that are not covered by the current price. Use that evidence to clarify the description or redesign the package. A service can be profitable on paper but difficult to deliver reliably if its scope is vague. Selstack connects the offer and booking workflow; the business still needs a realistic service model, accurate availability and a clear owner for every confirmed customer commitment.
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.
