Start with signup, then choose the job you need to do. This map indexes 268 documentation pages and 2503 section headings. It is a coverage map, not a claim that every workflow has passed a live test.
Video tutorials for this topic
Start by task
- Welcome: signup to first page
- Create a custom website
- Turn on live chat
- Bring your API credentials and email
- Create a customer dashboard
- Phone registration and employee assignment
- Appmint Mobile: CRM, chat, calls and events
Explore all functionality
268 guides available
AI skills · 45 guides
Bring a list of people into the CRM as contacts without emailing them, skip the ones already there, put them in a customer group and tag them, and check the group's count.
Inside: Ask first · Steps · 1. Customers & Benefits: who is already there · 2. Customers & Benefits: the new contacts · 3. Customers & Benefits: the group · 4. Customers & Benefits: the tags · When it's done · What it can't do yet · Don'tsAn AI assistant that answers visitors on the website chat or callers on one of the business's numbers, from the business's own reference text and records, with only the tools it needs — tested first, put live only after a yes.
Inside: Ask first · Steps · 1. AI Assistant: what it knows · 2. AI Assistant: the assistant, switched off · 3. AI Assistant: try it · 4a. Chat Designer: the website chat · 4b. Phone & SMS: a phone line · 5. AI Assistant: email, social and texts (only if asked) · When it's done · What it can't do yet · Don'tsAn AI employee hired for one job (sales, support, front desk) as a draft — its own user and groups, what it must ask a person before doing, its own mailbox and phone number — and switched on only after a yes.
Inside: AI employee or AI assistant? · Ask first · Steps · 1. AI Employees: the settings it starts from · 2. AI Employees: hire it, as a draft · 3. User Management: its access · 4. AI Employees: what needs a person's OK · 5. Email Accounts: its own inbox (if asked) · 6. Phone & SMS: its own number (if asked) · 7. AI Employees: switch it on · When it's done · What it can't do yet · Don'tsTurn "work every new lead", "follow up tickets that wait" or "send me a report at 5" into what an AI employee really acts on — its job description, an instruction for it, the channels it listens to, and work that arrives by assignment — each change shown before it goes live.
Inside: Ask first · How work reaches an AI employee · Steps · 1. AI Employees: what it is told · 2. AI Employees: the channels it listens to (if the job starts from inbound) · 3. Leads or Automation: the records it gets · 4. AI Employees: try it once · When it's done · What it can't do yet · Don'tsAn automation on any collection or record type that runs when a record is added, changed or deleted, narrowed to the records and changes that matter, built as a draft, tried on one test record, switched on with Start and followed on its monitor.
Inside: Ask first · Steps · 1. Collection builder: the record type and its field paths · 2. Automation: the draft · 3. Automation: try it once on one record · 4. Automation: switch it on with Start · 5. Automation monitor: the first real run · When it's done · What it can't do yet · Don'tsAdd the chairs, rooms, tables or seats a business books out, and tie them to a booking type so its bookings are limited to them.
Inside: Ask first · Steps · 1. Reservations: the service points · 2. Reservations: tie them to the booking type · 3. Open it · Say plainlyKeep the business's colours, fonts and logo in one brand design in Creative Studio, so every new graphic starts from a copy that is already on brand.
Inside: Ask first · Steps · 1. Files: the logo · 2. Creative Studio: the brand design · 3. Creative Studio: the logo in place · 4. Using the kit · When it's done · What it can't do yet · Don'tsTurn "everyone who…" into an audience a broadcast works out again at every send — a smart customer group for rules on contacts, or a dynamic list for rules on any collection (form signups, orders, carts) — previewed and counted first, then a draft addressed to it. A person sends.
Inside: Ask first · Rules · Steps · 1. Try the rules before saving · 2. Customers & Benefits (or Broadcast): save it · 3. Broadcast: the draft addressed to it · Advanced: a written query · Stop · When it's done · What it can't do yet · Don'tsHow a sent broadcast did — sent, delivered, opened, clicked, bounced, unsubscribed — for its latest run or an earlier one, who did what, why sends failed, and who is off the list for good. Read only; nothing is sent.
Inside: Ask first · Steps · 1. Broadcast: find it and its state · 2. Broadcast: the numbers · 3. Broadcast: the people behind a number · 4. Broadcast: who is off the list for good · Stop · When it's done · What it can't do yet · Don'tsTurn a Blueprint's design into the real system — each block built with the app that delivers it, each wire made real, and every record linked back to its block — stopping for a yes before anything goes out to people or costs money.
Inside: Ask first · Steps · 1. CRM Blueprints: read the design · 2. Get the build plan · 2. Build the blocks — in this order, each with its own app · 3. Make the wires real · 4. Show it · When it's done · Don'tsA page saved the way Build Studio stores it — one full HTML document per screen, page CSS in the head, page JavaScript in Page settings, and Appmint's own building blocks for anything live — at a URL nothing else owns.
Inside: Ask first · Steps · 1. Site settings: check the URL is free · 2. File manager: the images · 3. Build Studio: the page record · 4. Page settings → Style: the page's JavaScript · 5. Check it on the site · When it's done · What it can't do yet · Don'tsConnect the business's own domain for email — hosted mailboxes people read, a sending domain for newsletters, or both — give each mailbox to the right people or AI employees, and know which address mail really goes out from. DNS changes and agreements are a person's yes.
Inside: Ask first · Steps · 1. Email Accounts: what exists now · 2. Email Accounts: hosted mailboxes (the person's part) · 3. Email Accounts: a sending domain for newsletters · 4. Email Accounts: give mailboxes to people and AI employees · 5. Settings: which address mail really comes from · When it's done · What it can't do yet · Don'tsTake the business's number, decide who it rings, and how it answers — straight to people, to an AI, or through a menu that changes with business hours. Buying the number and switching live callers over are a person's yes.
Inside: Ask first · Steps · 1. Phone & SMS: the number · 2. Users & Groups: who it rings · 3. Phone & SMS: Direct Voice answering (no menu) · 4. IVR & Phone System: the routing record · 5. Phone & SMS: switch the number to IVR Menu · When it's done · What it can't do yet · Don'tsDesign a campaign's ads in Creative Studio, one frame per platform at its feed size, with the featured products' photos and the campaign's copy. The finished frames go back onto the campaign as its creatives, and a draft post can carry one. Nothing launches.
Inside: Ask first · Steps · 1. Marketing & Ads: the campaign and its copy · 2. Marketing & Ads: open Creative Studio from the campaign (the person) · 3. Creative Studio: the material · 4. Creative Studio: each frame · 5. Creative Studio: Use These Designs (the person) · 6. Social Media: a draft post (if asked) · When it's done · What it can't do yet · Don'tsA shop page that lists real products from the catalog and a product page that shows one by its slug, both with working add-to-cart buttons, a cart count in the header, and the site's checkout behind them.
Inside: Ask first · Steps · 1. Site settings: switch on the storefront · 2. Storefront: the products are ready · 3. Build Studio: the shop page · 4. Build Studio: the product page · 5. Check the cart and checkout · When it's done · What it can't do yet · Don'tsA new page made from an existing one — every screen, its page CSS and JavaScript — at its own name and URL, ready to change, with the original left exactly as it was.
Inside: Ask first · Steps · 1. Build Studio: read the source page · 2. Site settings: a free URL for the copy · 3. Build Studio: create the copy · 4. Build Studio: change what was asked · Templates from the platform · When it's done · What it can't do yet · Don'tsCreate and save a course in Content Studio, with lesson pages and a multiple-choice quiz whose right answers live in an answer key, then open it.
Inside: Ask first · Steps · 1. Content Studio: save the course · 2. Open it · Don'tsWrite a reusable email or text message template whose {{fields}} fill in from the customer, lead or booking it is sent about, preview it against a real record, and use it from an automation or a broadcast. Nothing is sent while building it.
Inside: Ask first · Steps · 1. Message Templates: the template · 2. Message Templates: preview against a real record · 3. Automation or Broadcast: use it · When it's done · What it can't do yet · Don'tsWrite a bulk email (a broadcast) addressed to one customer group, saved as a draft, with the audience counted. A person sends or schedules it.
Inside: Ask first · Steps · 1. Customers & Benefits: the group · 2. Email Accounts: the sender · 3. Broadcast: the draft · 4. Show it · When it's done · Don'tsBring in people or businesses (a search, the map, a file, the CRM), look up what is missing with any tool, find the right people at each company, rank them with the AI Classifier when asked, move the good ones into a pipeline or draft a broadcast — in the order the person wants, saved as a list that can run again.
Inside: Ask first · Steps · 1. Lead Finder: the list · 2. Lead Finder: the cost, then run · 3. Lead Finder: rank (only when the person asks) · 4. Leads or Broadcast: move or reach out (only when asked) · 5. Again later · When it's done · Don'tsAfter an email broadcast has gone out, a dynamic list of the people who got it but haven't opened it, worked out again when the follow-up sends, and a second email saved as a draft to that list. A person schedules or sends it.
Inside: Ask first · Steps · 1. Broadcast: the first email, and whether opens are counted · 2. Broadcast: the dynamic list of non-openers · 3. Broadcast: the follow-up draft · Stop · When it's done · What it can't do yet · Don'tsBring rows from a CSV or JSON file (or pasted rows) into a collection as a background import job, map the columns to fields, and follow it on the Jobs screen. Export works the same way in reverse.
Inside: Ask first · Steps · 1. Collection builder: the target collection · 2. Data import: map the columns and start the job · 3. Jobs: watch it finish · Export · When it's doneFacebook Lead Ads and a website form feeding one chosen pipeline, with the same person arriving twice kept as one contact.
Inside: How duplicates are handled · Ask first · Steps · 1. Social Media: the Facebook page (the person does this) · 2. Leads: where Facebook leads land · 3. CRM Forms and Automation: the website form · 4. Customers & Benefits: one person, one contact · When it's done · Don'tsTake the leads at a qualified stage, make sure each is a contact with an email, put them in one customer group, write three intro emails, and save them as three draft broadcasts (day 0, day 3, day 7). A person sends or schedules them.
Inside: Ask first · Steps · 1. Leads: the qualified leads · 2. Customers & Benefits: a contact with an email for each lead · 3. Customers & Benefits: the group · 4. Message Templates: the three emails · 5. Email Accounts: the sender · 6. Broadcast: three drafts · 7. Automation: the timing (only if asked) · Stop · When it's done · Don'tsA lead pipeline with its stages, scoring rules and assignment rules (who gets new leads), and a website form whose answers become leads on that pipeline.
Inside: Ask first · Steps · 1. Leads: the pipeline · 2. Leads: scoring rules · 3. Leads: assignment rules · 4. Collection builder: the record type for the answers · 5. CRM Forms: the form on that collection · 6. Automation: each answer becomes a lead · 7. The website · When it's done · Don'tsPut a product on Google Shopping, Facebook, TikTok, Amazon or another connected sales channel. Check the channel is connected, preview exactly what would be sent, fix what the channel would reject, and publish only after a yes.
Inside: Ask first · Steps · 1. Sales Channels: is the channel connected? · 2. Products: the product · 3. Preview: what the channel would receive · 4. Stop: ask before publishing · 5. Publish (only after the yes) · Don'tsWhen a lead arrives in a pipeline, it gets its owner, a welcome email from a message template and one of the business's email accounts, and a follow-up task if the lead hasn't replied after a set number of days.
Inside: Ask first · Steps · 1. Leads: the owner · 2. Message Templates: the welcome · 3. Email Accounts: the sender · 4. Automation: the draft · Calling the lead, and trying again · When they click a link in an email · When it's done · What it can't do yet · Don'tsCheck there is an account that can bulk-send, make a subscriber customer group, a signup form whose answers land in their own collection, a way to move signups into the group, and a first newsletter saved as a draft to that group. A person puts the link on the site and sends.
Inside: Ask first · Steps · 1. Email Accounts: the sender · 2. Customers & Benefits: the subscriber group · 3. Collection builder: where signups land · 4. CRM Forms: the signup form · 5. Customers & Benefits: signups into the group · 6. Broadcast: the first newsletter, as a draft · Stop · When it's done · Don'tsA skill is the training for one multi-app job — the steps in order, what each step produces, what the next step uses, and where to stop for a person.
Inside: What a skill page holds · Rules for every skill · Skills · Writing a new skillTake an order for a customer on their behalf, unpaid or paid outside the shop. Find or create the customer, put the products on an invoice saved as a draft, turn it into an order in their history, and send the invoice only when told.
Inside: Ask first · Steps · 1. Customers & Benefits: find the customer · 2. Products: the lines · 3. Invoices: the draft · 4. Orders: turn the invoice into an order · 5. Payment (only if it was paid outside the shop) · 6. Send the invoice (only when told) · When it's doneTake a product's photo into Creative Studio, cut out its background, put it on a clean colour or a generated scene, export it, and add it to the product's images when the owner says so.
Inside: Ask first · Steps · 1. Products: the photo · 2. Creative Studio library: the photo as an image item · 3. Creative Studio editor: cut out the background · 4. Creative Studio editor: what goes behind it · 5. Export: the person does it · 6. Products: the new image · When it's done · What it can't do yet · Don'tsAdd a product that comes in sizes and/or colours as real variants, each with its own SKU, price and stock, put it in a category, and give it a shipping weight and box size so it can be shipped.
Inside: Ask first · Steps · 1. Attributes: size and colour · 2. Products: the product and its variants · 3. Categories: put it in a category · 4. Publish (only when told) · When it's doneTurn "I sell X to Y" into AI Classifier rules (the questions every found contact is checked against) and the Lead Finder filters to start searching with. Nothing is searched or charged yet.
Inside: Ask first · Steps · 1. Leads (Lead Finder): the rule set · 2. Leads (Lead Finder): the first search · When it's done · Don'tsA registration form on the business's own website page that proves the visitor owns their email with an emailed code, takes one application per email, and has an automation, not the page, create the customer account.
Inside: Ask first · Steps · 1. Collection builder: the applications, one per email · 2. CRM Forms: the form, gated by an emailed code · 3. Automation: the customer account · 4. Site pages: request the code, then submit · When it's done · What it can't do yet · Don'tsWhere every AI employee stands, what is waiting for a person's OK (with the draft it wants to send), what each job really did and cost, its calls and its notes — and the person's own decisions, pauses and budget changes, made only when they say so.
Inside: Ask first · Steps · 1. AI Employees: where each one stands · 2. AI Employees: what is waiting for a person · 3. AI Employees: what each job did · 4. AI Employees: its calls · 5. AI Employees: its notes · 6. AI Employees: put things right (only when asked) · When it's done · What it can't do yet · Don'tsCreate a collection for the answers, a CRM form on that collection, set who may fill it in, and share it by link or invitation.
Inside: Ask first · Steps · 1. Collection builder — the record type for the answers · 2. CRM Forms — the form on that collection · 3. Share it · Doing something with each answer · When it's doneOne page named root whose first screen is drawn above every page and second screen below it, with the site's shared CSS and script in its Page settings; parent pages for a section's own band; and what wraps the built-in login, account and checkout pages.
Inside: Ask first · Steps · 1. Build Studio: the page named root · 2. Page settings → Style: the site's CSS, fonts and script · 3. Build Studio: parent pages (optional) · 4. Site settings: the built-in pages · When it's done · What it can't do yet · Don'tsGet a shared address like support@ into the Inbox, make sure each email gets a person or AI employee, and know how taking a conversation works. Built from a mailbox the platform reads and one automation, saved as a draft.
Inside: Ask first · Steps · 1. Email Accounts: the mailbox the platform reads · 2. Email Accounts: an AI employee for it (optional) · 3. Automation: a task for a person (optional) · How taking works, for the person · When it's done · What it can't do yet · Don'tsCheck that an order is ready for one-click shipping, fix what is missing (product sizes, packing, ship-from, sender phone, delivery address), then buy a label for every box. The order is marked shipped and the customer gets the tracking.
Inside: Ask first · Steps · 1. Orders: check the order · 2. Fix what's missing · 3. Shipping: buy the labels · 4. Print · When it's doneA text message to one customer group, saved as a draft from one of the business's own numbers — who can be texted, who said STOP, how many segments the text is and what one send costs. A person sends it.
Inside: Ask first · Steps · 1. Customers & Benefits: the group, counted by phone · 2. Phone & SMS: the sending number · 3. IVR & Phone System: STOP replies · 4. The message: plain text, with its opt-out line · 5. Broadcast: the draft · Stop · When it's done · What it can't do yet · Don'tsA graphic at the platform's size, in the business's colours and fonts, with their picture (or a generated one) and their words. Saved in Creative Studio, exported to Files and, if asked, attached to a draft social post.
Inside: Ask first · Steps · 1. Creative Studio library: the design · 2. Creative Studio editor: open it · 3. The brand kit and the size · 4. The picture · 5. The words · 6. Save · 7. Export: the person does it · 8. Marketing & Ads: the draft post (if asked) · When it's done · What it can't do yet · Don'tsA multi-page application in Content Studio — their details, uploads of their work (video, audio, photos), five words, and a quiz — sent to applicants and reviewed by staff.
Inside: Ask first · Steps · 1. Collection builder — three record types · 2. Content Studio — the application post · 3. Access — who can apply · 4. Invite applicants · Reviewing applications · When it's doneA form a new hire fills in before their first day — their details, emergency contact and a copy of their ID — saved into its own collection, open only to the invited person by magic link, and sent to them when the owner says so.
Inside: Ask first · Steps · 1. Collection builder — the onboarding record type · 2. CRM Forms — the form, invited people only · 3. Add the new hire as a participant · 4. Send it to the new hire · When it's doneSet up support so customers raise tickets from the website or their account, every ticket gets a number and an email, replies by email land back on the ticket, staff take, answer and close tickets, and urgent ones alert a person.
Inside: Ask first · Steps · 1. Email Accounts: the reply mailbox · 2. Tickets: types and the SLA workflow · 3. Message Templates: the ticket emails (optional) · 4. Site pages: where customers raise and follow tickets · 5. Automation: alert someone about urgent tickets · 6. Tickets: work a ticket · When it's done · What it can't do yet · Don'tsWhen nobody picks up, the caller can leave a voicemail, gets a text back from the business number, and the team gets an email about the call. Optionally, texts to the number get an automatic reply. Nothing is switched on for real callers until a person says yes.
Inside: Ask first · Steps · 1. Phone & SMS: voicemail · 2. Phone & SMS: tell the team about every call · 3. IVR & Phone System: missed-call actions · 4. IVR & Phone System: auto-reply to texts (optional) · Stop: switch it on · When it's done · What it can't do yet · Don'tsAppEngine API · 42 guides
API areas grouped by feature, with links to their deployed specifications.
Inside: Business Made · CRM · Users · Storefront · Stowbo · Community · Logistics · Repository · Finance · Affiliate · Everything elseDiscover the current deployment's API, read operation contracts and generate a client.
Inside: Search, then read the exact operation · Diagnose discovery failures · Turn discovery into an implementation · Generate a client from the selected deployment · How the reference is assembledLong-lived credentials for server-to-server access, and how they resolve to a user.
Inside: Using a key · Scope rules · Managing keys · Administration · Org users · Direct authentication · Blocking a keySign-up, sign-in, password reset and social login for the end users of a tenant.
Inside: Sign-up and sign-in · Password management · Social login · Profile · Subscriptions · Customer dashboards · Guests · Acting on a customer's behalf · Client-facing modulesGoogle, Facebook, GitHub and Microsoft — redirect flows and native token exchange.
Inside: Google · Facebook · GitHub · Generic customer social login · After a successful flow · OAuth for integrationsWhich credential to use for which kind of client.
Inside: Application and person tokens · Tenant and session rules · Where things live · Reference2FA setup and verification, device fingerprinting, trust and blocking, and login history.
Inside: Device fingerprinting · Managing devices · Login history · Two-factor authentication · When it is required · The challenge · Setup · Backup codes · Security settingsOperator sign-in, invitations, password management and session endpoints.
Inside: Password sign-in · Temporary passwords · POS passcode and NFC · Session · Invitations · Profiles · Magic links and codes · Shared-site access · Application registration · Global login · Guest accessHeaders, response envelopes, paging, error shapes, limits — the rules that hold across every endpoint.
Inside: Headers · Request bodies · Response envelopes · Single record · List · Paging and query options · Errors · Structured auth errors · Other common statuses · Rate limiting · CORS · Route aliasing · Timeouts · Health and versionImporting many records, streaming exports, and moving data between collections.
Inside: Bulk create · Export · Migration · Tracking a migration · AggregationsDefining your own datatypes, how schemas drive both validation and UI, and repairing a collection.
Inside: Reading collections · Schemas define data and UI · Repairing a collection · Search indexes · Settings · SubschemasUpload, thumbnails, signed URLs, privacy, and the org-scoped storage layout.
Inside: Identity and API-key scopes · Uploading · What an upload does · Thumbnails · Reading files · Managing files · Listing · Favicons · Customer-scoped files · Stock media · Assets · Storage configurationState transitions, versioning, restore from history and trash, and per-record permissions.
Inside: States · Approval · Publishing · History · Trash · Per-record permissions · Workflow and notes · ActivityThe four shapes a page record can take, how the renderer chooses between them, where page CSS and JavaScript live, and how to write a page without losing what was there.
Inside: The four shapes · Taking ownership of a page · Checking what a page actually has · How data.html is rendered · Where page CSS and JavaScript go · Writing a page · Creating a page · Wrapper pages · Verifying a deploy · RelatedGeneric records, exact lookup, pagination and guarded create/update/delete operations.
Inside: Create · Variants · Find a page · Read · Update · Delete · Search · Aggregate · Categories and tags · Settings · Organizations · Preview · AI-callable methodsThe site record — the home page, hosts and domains, logo and favicon, tracking and SEO — and the two fields whose shape is not what you would expect.
Inside: The fields · homePage — name, slug or id · favicon is a string. logo is an object. · Hosts and domains · Tracking and SEO · Chrome switches · Writing to the record · RelatedConnect an AI client to AppEngine over the Model Context Protocol — discover services, read their signatures, and call them.
Inside: Endpoint · Authentication · Client configuration · The three tools · Checking it works · How services get exposed · RelatedChat, agents, MCP tools, image and video generation, AI employees, voice, and API discovery through MCP.
Inside: Chat and agents · MCP tools · Image and video generation · CRM AI assistant · AI employees · Voice · API discovery for agents · Usage and costAsking for access to a screen or a guarded operation, and deciding it from a tray, through the org's workflows.
Inside: Routes · Asking · Deciding · Tray and history · AI employees · access_requestEvent-driven automations, AI-generated flows, and the generic task workflow engine with SLAs.
Inside: Automation · How an automation is built · AI-assisted authoring · IVR · Workflow · Definitions · Firing work · Tasks · SLAs and escalation · Analytics · RelatedBank linking for the books — connect accounts through Plaid, read balances and transactions, and reconcile them. Read-only; no money moves.
Inside: Connecting · Balances · Transactions and reconciliationThe endpoints behind BusinessMade — people, time, pay, benefits, bills and the ledger.
Inside: Setup and seeding · Employees · Timesheets and time clock · Payroll · Runs · Pay stubs · Employee payroll profiles · Employer tax setup · Reports · Paying a run: bank file, Stripe ACH or Plaid Transfer · Government e-filing · Books · Accounts and journals · Reports · Automatic posting · Period close · Bills and vendors · Recruitment · Onboarding and offboarding · Leave · Benefits · Performance and learning · Compensation · Organization · Documents and policies · Workforce readiness · Schedules · Work orders · Employee self-serviceThe signed-in customer's own account — profile, orders, forms, reservations, tickets, messages, addresses, wishlists, files, benefits, shared accounts and payment links.
Inside: Who "me" is · How it differs from /repository · Guards · Dashboard · Profile and verification · Orders, forms and transactions · Reservations · Tickets, messages and notifications · Addresses and wishlists · Files · Benefits · Shared accounts · Payment links · Also herePages, posts, stories, follows, connections, direct and group messaging, meetings, blocking and reporting, plus social-listening topics.
Inside: Who may write · Pages · Feed, posts and comments · Reactions and hashtags · Stories · Follows, bookmarks, notifications, badges · Announcements · People · Group chats · Connections, direct messages, meetings, blocking · Media · Live chat socket · Social listening topics · DatatypesPosts taken page by page — courses, applications, trainings, documentation — with outline, access, progress, answers, marking and review.
Inside: The post · Conditions · Customer routes · Staff routes · post_progressThe design library and the editor's save path — searched and paged listings, new designs, saves, copies, previews and uploaded images.
Inside: Routes · Library · Designs · Uploaded imagesLeads, pipelines, campaigns, ads, tickets, reservations, signed documents and the AI assistant.
Inside: Leads · Pipelines · Scoring and enrichment · Importing · Forms · Tickets · Reservations and appointments · Signed documents · Marketing campaigns · Audiences · Paid advertising · Ad accounts and readiness · Google Ads · Auto-campaign · AI assistant · Inbox and messaging · Communications · Customer activity · Promotions · Merchant customers · Social · Also hereThe server side of Device Hub — hub keys and live state, remote peripheral config, device calls, and the event stream back to screens.
Inside: Hubs · Calling a device · Events from hubs · The hub socketEvents, ticket types, sessions, QR validation, badges, credentials, check-in and event media.
Inside: Events · Tickets · QR and validation · Fulfillment · Perks · Badges · Sessions · Check-in and occupancy · Participants · Credentials · Event media · Attendee endpoints · Live check-in queue · DatatypesInternal balances, payout workflow, and gateway-agnostic payment operations.
Inside: Wallets · Movements · Payouts · Payments · Customer-facing · RelatedWho is dealing with a record — take it, finish it, give it back — on any datatype, for people and AI employees alike.
Inside: Routes · Lifecycle · The handling fieldDelivery jobs, pricing quotes, zones, drivers, live tracking, proof of delivery, customer orders with payment, and driver earnings and payouts.
Inside: Who may call · The delivery lifecycle · Pricing and addresses · Zones · Drivers · Jobs and assignment · Driving the job · Money, proof, issues and messages · Driver app · Earnings and payouts · Ordering a delivery · RelatedPhone numbers, inbound call routing, SMS keywords and auto-replies, email broadcast and live chat.
Inside: Phone and voice · Numbers · Pointing a number at a flow · Four ways to answer · Forwarding groups · Hours and misses · Softphone · SMS · Registration · Inbound routing · Opt-out · Email · Chat · Provider connections · RelatedUsage metering and token balances, monitoring and analytics dashboards, vendor connections, upstream integrations and cluster management.
Inside: Usage · What gets metered · How a request is charged · Balances and history · Service pricing · Monitoring · Analytics, stats and overviews · Connect · Upstream · Cluster management · RelatedRender a record as a full-page PDF or as thermal receipt lines, from built-in templates.
Inside: Routes · What is printable · What a template seesThe two-layer model behind configurable products — the reusable definition, the per-product subset, every attribute type, file uploads, the required rule and how option prices reach the order.
Inside: sf_attribute · sf_product.attributes[] · Storage · Option presentation · Types and controls · File attributes · The required rule · Pricing · Order persistence · RelatedSelling the same catalog on Amazon, eBay, Etsy and elsewhere — mappings, inventory sync, order aggregation and pricing.
Inside: Channels · Mappings · Categories · Attributes · Templates · Transform and validate · Inventory sync · Orders · Pricing · Listing optimization · AnalyticsEveryone who works in the org — people and AI employees — with what a colleague needs to reach them.
Inside: Routes · What a row holdsCatalog, cart, checkout, payments, orders, POS, inventory, pricing, discounts, returns, rentals and tax.
Inside: Catalog · Cart · Checkout · Payments · Orders · Point of sale · Inventory · Pricing · Discounts · Gift cards · Invoices · Returns · Rentals · Tax · Shipping · Syndication · SubscriptionsSpace custody — listings, carts and holds, bookings with per-item sessions, movements, delegated pickups, fees, settlement and host payouts.
Inside: The model · Checkout · Guest routes · Delegated pickup · Host routes · Operator routes · DatatypesTeam workspaces and conversations — members, a journal of messages, files, tasks, meetings and agendas, with a personal Home, Inbox, My Tasks and My Calendar.
Inside: Who sees what · Home · Workspaces and conversations · Members · The journal · Tasks, meetings and views · Maintenance · Live updatesWhat AppEngine exposes, how it is organized, and how to find the endpoint you need.
Inside: Finding your way around · The APIs · Client-facing route pairs · Global behavior · Where to go nextAppmint Chat · 2 guides
Where your team works chats — queue, presence, transfers, AI handover, calls, screen sharing and broadcast.
Inside: Three views · Going on shift · The queue · Working a conversation · Handing a chat to someone else · AI handover · Proactive engagement · Calls · Screen sharing and broadcast · What the visitor sees · Proactive notices · Sessions · Archiving · RelatedAn embeddable chat widget with live agents, queueing, presence and AI answers — dropped onto any site with two script tags.
Inside: What it gives you · Embedding it · Configuration · Two modes · Skipping the registration form · Attachments · Languages · How a conversation flows · Presence · Customer context · Voice and video · RelatedAppmint Mobile · 40 guides
The queue behind the Check-in screen — the workflow it runs on, what each host action writes, the notifications it sends, and the other pipelines the platform creates for you.
Inside: The pipeline · A task is the queue entry · Getting into the queue · Host actions · The "table ready" message · Wait times and SLAs · The other built-in pipelines · When something goes wrong · RelatedConnect printers, scanners, card terminals and staff-access readers to a mobile workstation.
Inside: Choose a connection · Receipt and ticket printer · External barcode scanner · Use the scanner in the right screen · Card terminal and Tap to Pay · NFC staff access · Cash drawer · Daily readinessConfigure zones, capacities, scan points, ticket access and benefit counters.
Inside: Zones and scan points · Re-entry policy · Benefit counters · Accreditation rules · Staff procedureBusiness locations, the service points inside them, their statuses, and which part of the platform is allowed to change each one.
Inside: Locations · Service points · Creating and editing from the app · Statuses and who sets them · Seating rules worth knowing · RelatedThe product fields the point of sale reads, day-parts and the 86 list, the per-location overlay, and how selling draws stock.
Inside: Product fields the POS uses · Modifiers and stations · Day-parts and the 86 list · Taking an item off sale · The per-location overlay · Stock · Pricing is decided on the server · When something goes wrong · RelatedWhich emails and texts the platform sends for the things this app does, where the templates and copy-to settings live, and what push actually exists on mobile.
Inside: What gets sent, and when · Where to change the wording · Copy-to and sender settings · Staff communication · Nothing arrived — check in this order · Related · Find a sent messageReservation definitions, services, hours and slots — what to configure so the booking wizard offers the right times, and what the app can and cannot change.
Inside: Setting one up, in order · The definition · Slots · Booking from the app · Reservation statuses · What the app can and cannot edit · When something goes wrong · RelatedWho can sign in, how quick sign-in and NFC access cards are controlled, and what happens when a device is blocked or an account is removed.
Inside: Two kinds of identity · What each person sees · Sign-in methods available · Two-factor verification · Quick sign-in settings · Passcodes · NFC access cards · Saved sessions and shared devices · Blocked devices and forced sign-out · Removing an account · When something goes wrong · RelatedUnderstand which settings belong to a workstation, staff account or organization.
Inside: Setting ownership · Closing the app and signing out · Account security and shared dataAssign the workstation, maintain its business address and connect the location’s card terminal.
Inside: Assign the workstation · Maintain the business address · Configure the card terminalConfigure a workstation for front desk, service, production, sales, events or field operations.
Inside: Choose a layout · Return to the full launcher · POS settings · Prep controls · Payment choices · Business location · Shared devicesWhich backend a build talks to, how the development and production environments are chosen, and what the app stores on the device.
Inside: The two environments · Derived behaviour · Organization and tokens · Legal and support links · Platform identifiers · RelatedThe server-side settings the app reads — quick sign-in, locations, payment gateways, receipt templates, workflows, rate limits — and one security note about the storefront routes.
Inside: Quick sign-in · Locations · Payment gateways · Receipt and check templates · Workflows · Notification senders and copies · Rate limiting · What the app does not read · RelatedConfigure payment choices, terminals, tips, split tenders, recovery, refunds and receipts.
Inside: Configure the organization and device · Payment methods · Connect a terminal · Tips and split tenders · Payment confirmation and recovery · Refunds · ReceiptsPrint checks, receipts, prep tickets and event admission codes from mobile.
Inside: Set up a printer · Choose the document · Print after payment · Event admission QR codes · Shared printers and preparation · Daily careHow the app boots, how state and networking are layered, and which services talk to which part of the platform.
Inside: Boot sequence · Providers · Navigation · Networking · Services layer · Theme · RelatedThe Dart models under lib/models, the server datatypes they map to, and the fields and enums that matter.
Inside: Models → datatypes · POS: sf_order and PosOrder · service_point · reservation and reservation_definition · task payloads · CRM records · About bmlocationproduct · RelatedEvery route Appmint Mobile calls, grouped by module, with the auth each one actually enforces.
Inside: Auth and profile · Passcodes and access cards · Storefront: POS tabs · Storefront: payments · Repository (generic records) · Reservations and service points · Check-in queue · Workflow · CRM · Chat and presence · Phone and softphone · Events (staff side) · Social sync · RelatedPlan the mobile environment, hardware transports and connected business workflows.
Inside: Identity and context · Native services · Payment lifecycle · Event lifecycle · Documentation and integration referencesEvery folder under lib, what each screen class is for, and which root documents are still accurate.
Inside: lib/ · Screens · auth/ · dashboard/, home/, more/, profile/, calendar/ · pos/, payments/ · operations/ · events/ · CRM and communications · settings/ · Root documents · RelatedVersions, identifiers, permissions and the exact App Store and Play upload flow that has worked.
Inside: Identifiers · Permissions · iOS: App Store · Android: Google Play · Android: direct APK while Play is in review · What is in the repository that should not be · Release checklist · RelatedUse the project toolchain, target the intended backend and run the native mobile app.
Inside: Prepare the toolchain · Connect to the intended environment · Native launch · Verification commands · Workflow verificationSet up Appmint Mobile for your organization, staff role and daily work.
Inside: Sign in · Choose the device's tools · Assign the business location · Connect hardware · Choose the first workflowSales, service, events, communications and team operations on your phone or tablet.
Inside: Explore the app · Choose a workspace for the job · Locations and shared records · Phones, tablets and hardware · Get startedA full shift end to end — open the floor, seat from the queue, take and fire orders, settle, release tables, and handle no-shows.
Inside: Before doors · As parties arrive · Seating · Ordering and firing · Mid-service moves · Settling · Releasing the table · When things go wrong · Closing · RelatedQuick sign-in with a passcode or card, saved sessions, switching organizations, and what the location picker scopes.
Inside: Quick sign-in · Saved sessions · Switching organizations · The assigned business location · Home layout · What is per device and what is not · RelatedScanning, searching, the scanner modes, refresh habits and what needs a connection — the small things that make a busy shift faster.
Inside: Scan instead of typing · Hardware scanners: pick the mode · Search everywhere · Refresh · The home screen · The tab strip · What needs a connection · Small habits that add up · RelatedCheck access, context, connectivity, hardware and transaction state when assisting an operator.
Inside: Account and app access · Working context · Hardware readiness · Payments and receipts · Event admission and benefits · Customer communication · Request assistanceManage leads, contacts, customer context, support, tasks and meetings while away from the desk.
Inside: Leads · Contacts · Customer journey · Support tickets · Tasks · Meetings · A field-agent routineSell, issue, comp, fulfill and print event tickets at the desk.
Inside: Prepare the desk · Sell tickets · Issue and complimentary tickets · Collect an existing booking · Register a walk-in · Ticket printingManage schedules, participants, attendance, occupancy and the event working context.
Inside: Overview and event selection · Info Center · Schedule · People · Statistics and occupancy · Management and activityRun ticket sales, accreditation, admission, exits, re-entry and benefit redemption from a phone or tablet.
Inside: Set up an event workstation · Set the scan point · Entry and continuous scanning · Exit and re-entry · Capacity and zone access · Benefits and entitlements · Ticket lookup · Sales and accreditationFind the guide for every Appmint Mobile job.
Communicate with customers through email, SMS, messaging, website chat and the business softphone.
Inside: Unified inbox · Email · SMS and other channels · Live Chat · Human and AI collaboration · Live Presence and customer journey · Business softphone · Coordinate a customer handoffManage sign-in, organization context, quick access and workstation settings.
Inside: Sign in and choose the organization · Quick sign-in · Find the settings · Layout and staff accessThe four operations screens — Tabs, Floor, Reservations and Check-in — and how a party moves between them.
Inside: Tabs · Floor · Reservations · Booking a reservation · Check-in and Arrivals · The jobs, step by step · How a party moves · When something goes wrong · RelatedRoute and manage work through prep stations, production stages and service workflows.
Inside: Picking a workflow · What a task shows · Stations · Working a ticket · Refires and duplicates · The manager view · When something goes wrong · RelatedScan products, manage tabs, send selected items to prep, collect payments and deliver receipts.
Inside: Products and the cart · Continuous product scanning · Save and reopen a tab · Send selected items to prep · Checkout, tips and split payment · Resume a partially paid order · Continue an interrupted payment · Receipts and reprints · Refunds · Daily controlsCharge an amount that is not on a menu — a deposit, a service fee, a phone order — through the same checkout as a tab.
Inside: What it does · Taking the money, method by method · Where it goes · If you stop halfway · When something goes wrong · RelatedFollow shared work, direct AI employees and manage approval decisions from mobile.
Inside: Workspaces · AI employees · Approvals · A mobile supervision routineBilling · 4 guides
Why a service must be accepted before it runs, and where the current terms are served from.
Inside: The base terms · The four setup agreements · The per-provider agreements · Why it is required · What happens without acceptance · Acceptance is recorded per service · Which services need one · Where to see what you have accepted · RelatedBalance, provider cost, platform markup, subscriptions and what happens when funds run out.
Inside: Balance · What you are charged · Markup varies by service · Bring your own credentials, and the markup goes away · Subscriptions · Zero-cost usage · Running out of balance · Usage reporting · For the platform operator: Service Usage · Credit between organizations · RelatedEvery subscription plan, what it costs monthly and annually, and the limits attached to each.
Inside: Studio Manager · Platform · BusinessMade · What the limits mean · Enterprise · Reading plans programmatically · RelatedEvery metered service, its unit, its markup, and the underlying provider rates.
Inside: The metered services · Tiered services · Bulk email · Google Maps and address lookup · AI model rates · OpenAI · Anthropic · Google Gemini · DeepSeek · Image generation · Working out a cost · Reading rates programmatically · RelatedBuilding on Appmint · 13 guides
Getting hundreds of products in from JSON — the record shape, images, the fields that are not where you expect, and making the load re-runnable.
Inside: The record · isNew: True is required · Categories and tags go in post, not data · name is truncated at the top level · Images are objects, and there are two fields · Images · Make it re-runnable · Take a range · Order of operations · Updating, not creating · Migrating from another platform · ChecklistAn on-canvas text editor with fonts, rotation, arc-curving and live pricing — 113 KB of JavaScript in one page record, read end to end.
Inside: The shape · The catalogue is embedded, not fetched · The readiness gate · One state object · Fonts the canvas can actually use · Curved text · Dragging · Pricing, and who is allowed to decide it · The configuration has to survive as words · The single write · What this demonstrates · Where it would stop workingThe two-layer attribute model behind custom products — a shared definition, a per-product subset, file uploads, the required rule, and how option prices reach the server.
Inside: Two collections · Presentation is not the answer · Storage · The types, and what each renders as · File attributes · Per-file notes · Placement on a mockup · The required rule · Getting the price to the server · What survives to the order · ChecklistHow your site plays posts — blog posts, galleries, courses, applications and trainings — page by page, with progress, conditions, review and preview.
Inside: Turning it on · What a visitor sees · Sign-in and progress · The page contract · Review · Preview · In codeRendering live records into a page — declaratively with a handful of attributes, or in code when the markup stops being enough.
Inside: The declarative route · What data-payload accepts · The template flash, and why it is handled · Formatting · Reading in code · Which to use · Three states, every time · Rendering safely · Pagination · RelatedKeyword search and reactive filters, plus the stats API behind views, likes, favourites, shares and ratings — including the three rules that make it behave.
Inside: Search · Reactive filters · The stats API · Three rules · Counting views · RelatedThe production pipeline — author a site as plain HTML you can open from disk, then deploy it to page records with one command, safely and repeatably.
Inside: The source folder · What the deploy script does · 1. Inline the stylesheet · 2. Rewrite internal links · 3. Extract metadata · 4. Attach the page's JavaScript · The write · The id map · Deploying one page · Verifying · Status codes are not enough · Crawl your own links · Look at it · Shared chrome · Things that bite at scale · ChecklistThe advanced track — what you can actually build on Appmint, the three places your code can live, and how to choose between them.
Inside: Three places your code can live · How far option 1 actually goes · When to stop · What you need to know first · The sectionThe two stores available to a page application — the runtime's reactive state and your own object — what each is for, and how to redraw without a framework.
Inside: The runtime store: appmint.state · What it costs · Use it for · Your own object · Why not put that in state? · Rendering without a framework · Full redraw, not patching · Rebinding after a redraw · Deriving, not storing · The three states every bound region needs · ChecklistEvery trap in this section listed by what you actually see, because at 2am you search for the symptom, not the cause.
Inside: Quick index · Page deploys, nothing changes · Your JavaScript never runs · getElementById returns null · create => record is not marked as new · Form "not available for public access" · Reservation Definition not found · Booking returns 401 · Favicon does not change · Site renders unstyled · Nav links 404 · One click, two records · Prices and images disappeared · Products load but categories are empty · Product tiles are blank · Upload path doubled · SVG will not render · 403 error code: 1010 · 404 customer … not found · data-bind renders blank · Configured options are not charged · [object Object] in a price · Canvas text, wrong font · A page answers 404 · Order missing choices · Global is undefined · Emails never arriveYou can read any datatype from a page. You cannot write one the same way — and the three routes out of that, with the cost of each.
Inside: Reads are general. Writes are not. · Where writes do exist · The three routes out · Route 1 — A CRM form · Route 2 — Call the API from your page code · Route 3 — Your own server · Choosing · What this means in practiceThe four signals that you have outgrown a page application, and what the crossing actually costs — from a marketplace built headless over AppEngine.
Inside: The four signals · 1. You need to write repeatedly as the user works · 2. A credential must never reach the browser · 3. You need routing with real state between views · 4. You depend on a build step · What you get, and what you take on · The shape · The session · A typed layer over the endpoints · What it costs · When the API does not have your endpoint · The honest recommendation · NextThe page record's style.javascript field, the readiness gate every page app needs, and when the script tag in your HTML runs and when it doesn't.
Inside: style.javascript, on the record · The readiness gate · If it seems not to run · When the <script> in your HTML runs · What does survive · The fallback: an attribute bootstrap · Do not split handlers from your code · Make it idempotent · ChecklistClient Integration · 17 guides
Application identity, customer identity, request-owned sessions, and what the JavaScript SDK actually automates.
Inside: Application exchange · Establish the visitor session · Browser transport versus example cookies · Read, refresh and end the session · Domain resolution and telemetryThe endpoints a client application actually calls — auth, catalog, cart, checkout, orders, and the customer-scoped client/* surface.
Inside: Authentication · Catalog · Pricing, shipping and discounts · Checkout and orders · The client/* surface · Content Player — client/content-studio · Notes that save a debugging session · Anything not listed hereThe error envelope, the codes you must handle, and what each one actually means.
Inside: Codes worth handling · Validation is strict · Failures that are not errors · Proxy your errors faithfully · JavaScript transport failuresSelect the actual web or mobile example, install its own dependencies, and verify its implemented scope.
Two kinds of people, three endings to a sign-in, verification codes, shared devices and remembered accounts.
Inside: Two identities, kept apart · Sign-in has three endings · Finishing a verification · Signup and user fields · The other ways in · Staying signed in · Remembered accounts · Changing organization · What is not here · RelatedThe package that talks to AppEngine from Flutter — app authentication, staff and customer sign-in, and reads and writes over any datatype.
Inside: Getting the code · Connect once · What it covers · The shape of it · Storage · Configuration and lifecycle · Offline · Related · Current SDK guide and compatibilityThe SDK's network behavior, scoped read caches, uncertain writes, and recovery after reconnection.
Inside: Storage boundaries · Fall back only for a network failure · Reconnection and lifecycle · Writes with an unknown outcome · What can be stale · Sign-out and organization changesReads and writes over any datatype, the escape hatch for everything else, and what the errors mean.
Inside: Datatypes, not tables · Reading · Writing · Everything else · Multipart uploads · Chat and attachments · Watching what it does · Errors · Related · Current AppEngine account-write restrictionsIntegrate the Flutter client with sign-in, verification, session restore and a protected read, using the complete authentication sample.
Inside: Run the complete reference app · Step 1 — Create the project · Step 2 — Add the client · Step 3 — Connect to your organization · Step 4 — Sign somebody in · Step 5 — Handle the verification code · Step 6 — Show the session, and read something · Step 7 — Stay signed in, and sign out · Run it · When it does not work · Where to go nextwindow.appmint — the JavaScript API that HTML pages and no-code markup use to reach the platform, and how it bridges to the host application.
Inside: How it is built and loaded · The bridge · Namespaces · Reaching an endpoint with no wrapper · Declarative markup · Cart totalsBuild your own site, app or storefront on the AppEngine API — the call path, the clients, and runnable examples.
Inside: Start here · Building for mobile · Reference · The call path · When a direct call is fine · Separate the available clients · Money comes from the server · Current client compatibilityRun a server-side application exchange, list products, and calculate a controlled cart with native fetch.
Inside: 1. Set server configuration · 2. Save and run the request · 3. Understand the response · 4. Add customer ownership separately · Diagnose the first failureThe WebSocket surface — connecting, authenticating, the event vocabulary, and why this is the one case that talks to AppEngine directly.
Inside: Connecting · Authenticating · Event vocabulary · Streaming replies · Reconnection · Embedding · Other namespacesCurrent JavaScript and Flutter behavior, route changes, session boundaries and source-verified integration guidance.
Inside: Important differences and current alternatives · AppEngine-specific sequences · Source basisA concrete request-owned Next.js pricing route, and the boundaries of the shipped Next.js, Remix, and hosted renderer gateways.
Inside: A pricing route with the source SDK · When adapting the example catch-all · Session and isolation checksInstall the source package, configure a request-owned client, call the implemented helpers, and handle current SDK/backend differences.
Inside: Install from a source checkout · Configure a server client · Configuration and transport · Catalog and pricing · Implemented helper reference · Authentication and failures · Verify before connecting customers · Customer registration, renewal and sign-out · Ordinary bearer mode and transport adapters · Environment supportDevelop against the checked-in Next.js storefront, trace catalog and pricing, then add explicit server validation and customer ownership.
Inside: 1. Start the project · 2. Read the catalog on the server · 3. Trace the browser cart · 4. Put validation in a dedicated route · 5. Add a session before private customer data · 6. Separate quote, saved cart and checkout · 7. Verify the extensionDevice Hub · 5 guides
The Devices and Hubs screens in BusinessMade — diagnosing, editing, rotating keys and moving locations.
Inside: The hub card · Diagnose · Editing a hub · Rotating the API key · Adding devices · Deleting · RelatedPeripherals are discovered by the hub — you connect the ones you want. Plus what each device type needs.
Inside: The flow · Reading the peripheral list · Direct versus remote · Adding a device by hand · What each device type needs · Receipt and kitchen printers · Barcode and QR scanners · NFC and RFID card readers · Cash drawers · Displays, KDS, scales and terminals · Naming · RelatedConnects in-venue USB peripherals — printers, scanners, cash drawers, NFC readers — to the platform.
Inside: What this means in practice · What it connects · How it works · What it runs on · Setup · Shared versus paired hardware · RelatedCreate the hub, install the agent on a venue box, and pair it with your organization.
Inside: 1. Pick a box · 2. Create the hub · 3. Install the agent · The setup wizard · Where things land · Verifying the download · 4. Confirm it connected · How it connects · NextWorking through a hub or device failure in the right order.
Inside: The hub will not come online · Nothing prints · Output is garbled or wrapped wrongly · The drawer will not open · Scanning does not work · Card taps do nothing · A device disappeared from the list · Reading the peripheral statuses · The hub is locked out after a key change · Changes are not sticking · Everything works except from one device · Getting help · RelatedEventOxygen · 29 guides
Pages, announcements, stories, moderation, connections and what staff can do from the admin side.
Inside: Pages · Announcements · Stories · Moderation · Hashtags and trending · Connections · Meetings · Group chats · Badges · Staff versus attendee surface · RelatedRunning the event from Appmint Mobile — the event shell, scanning and check-in, the accreditation desk, badges, live numbers, and what is not wired up yet.
Inside: Who uses what · Before doors open · Ticket scanning and check-in · Accreditation and badges · Tickets tab · People, schedule and the info center · Live numbers · Leads · Venue displays · Handling problems on the day · Not in the app yet · RelatedThe event record, sessions, ticket types and participants — every field the attendee app and the door depend on.
Inside: The event record · Status lifecycle · Venue versus address · Scan points · Accreditation points · Settings · Sessions · Ticket types · Participants · Cover images · What the server checks at the door · RelatedEvery email, SMS and in-app notification the event and community modules send, what triggers it, and what push actually exists.
Inside: Platform notifications · Copies and senders · Community notifications · What attendees see and when · RelatedRunning the door — check-in, accreditation, badges, occupancy and the live dashboard.
Inside: Before the doors open · Checking people in · Will-call · Accreditation and credentials · Badges · Perks · Leads · Watching it run · Troubleshooting · RelatedHow a purchase becomes tickets, how QR codes rotate, and what transfer, comp, fulfil, cancel and refund each do to the numbers.
Inside: Purchase rules, in order · Booking lifecycle · Ticket statuses · QR codes · Transfers · Comps, stock and activation · Fulfilling at an accreditation point · Cancel, refund, delete · Credentials · Badges and perks · Notifications along the way · RelatedWhich backend, organization and keys the app is built against, and the headers every request carries.
Inside: The two environments · App credentials and tokens · Headers on every request · Legal and support · Activity tracking · RelatedWhere event photos, cover images and attendees' own uploads live, how signed URLs work, and the limits worth knowing.
Inside: Event media and signed URLs · Cover images · Attendee uploads · Practical limits · RelatedThe organization and site the app belongs to, what is public without a token, rate limiting and the server variables behind events and community.
Inside: Organization and site · Event-level settings · Notification settings · What needs no token · Rate limiting · Server variables · RelatedHow a ticket purchase is charged — Stripe intents, the payment sheet, confirm-order, free events, guest checkout and what the web build does instead.
Inside: Where the publishable key comes from · The purchase flow · Free events · Guest checkout · Other checkout routes · Refunds and cancellations · Currency · RelatedHow the attendee app boots, its two shells, the two-token HTTP client, and the services behind tickets, community and chat.
Inside: Boot sequence · Shells and navigation · Providers · Networking · Real-time chat · Activity tracking · Theme · Not implemented · RelatedThe event, ticket, session and participant records, the community records behind the feed and chat, and the rules the server enforces on each.
Inside: Events · Community · Customer · RelatedThe client/events and client/community surfaces the attendee app uses, the auth calls around them, and the chat socket events.
Inside: Auth and profile · Events and tickets · Purchase · Community: pages and feed · Community: people and connections · Community: messages, notifications, meetings, bookmarks · Media · Activity · Chat socket · Staff-side counterpart · RelatedWhat the September 2026 test passes fixed in the app and on the server, what is still open, and the dead code to ignore.
Inside: Fixed on 2026-09-03: events · Fixed on 2026-09-03: community · Still open · Dead code and unimplemented features · Security notes · RelatedEvery folder and screen in the EventOxygen codebase, plus which root documents describe the current app and which are history.
Inside: lib/ · Screens · auth/ · customer/ — shells and events · customer/ — people and community · Root documents · scripts/ · RelatedIdentifiers, the EventOS versus EventOxygen naming, and the App Store and Play upload flow.
Inside: Identifiers · Environment at build time · iOS: App Store · Android: Google Play · What ships and what does not · Release checklist · RelatedDebug builds, the phone-sized web build that lets you drive the app from Chrome, the dev login, and the seed scripts.
Inside: Prerequisites · Debug builds · Running on web at phone size · Static checks and tests · Seeding an organization · Working against the backend · Verifying social features · RelatedInstall the app, sign in, find your event, and get your ticket in front of you.
Inside: Install it · Do you need an account? · Signing in · Finding your event · The two shapes of the app · Getting set up for the day · NextYour all-in-one event companion — tickets, badge, schedule and networking, with check-in and live dashboards for organizers.
Inside: Who it is for, and how you get started · Getting it · For attendees · Guides · For organizers and staff · Ticketing · Perks · Sessions and speakers · Leads from badge scans · Running the door · The event lifecycle · What it suits · RelatedThe checklist before you travel, what needs a connection, switching events, multiple tickets, guests and sharing a booking.
Inside: The night before · What needs a connection, and what does not · At the door · Several events, several tickets · Guests and the booking email · Sharing a booking · Speed · RelatedUsing the directory filters, follow versus connect, meeting requests that confirm, bookmarks, shares and hashtags well.
Inside: Work the directory by type · Follow first, connect second · Requests: yours and theirs · Meetings that actually happen · Bookmarks as a working list · Share into a conversation · Hashtags for a track · Keep notifications useful · RelatedSign-in, missing tickets, empty schedules and directories, feed and comment errors, chat, payments and slow images — in the order worth checking.
Inside: I cannot sign in · My ticket is not showing up · The schedule says "No sessions on this day" · People is empty, or the profile shows an id instead of a session · "Couldn't load the feed" versus "No posts yet" · A comment failed with "Database operation failed" · My like does not show · A repost is a blank card · The drawer lists the same event twice · Chat is not live · Payment does nothing on the web version · Images are slow or blank at first · Everything is slow · Before asking for help · RelatedThe two shapes of the app, what the event home shows, the calendar-based schedule, the media gallery and the drawer.
Inside: Two shapes of the app · Event home · Schedule · Media · The drawer · RelatedThe Explore feed — posting, polls, reactions, comments, sharing, reposts, bookmarks, stories and announcements.
Inside: What the feed is · Writing a post · A post card · Your own posts · Post detail · Hashtags, search and trending · Announcements · When the feed cannot load · RelatedMessage threads, the chat screen, sending photos, starting a new conversation, and the Notifications tab.
Inside: Messages · The chat screen · Starting a conversation · Notifications · RelatedYour profile, editing it, your QR card, your media library, legal and support links, signing out and deleting your account.
Inside: The Me tab · Editing your profile · Your QR card · Media library · Legal and support · Signing out · Temporary passwords · Deleting your account · RelatedConnecting with people, your QR profile card, handling requests, messaging and how scoping works.
Inside: Set your profile up first · Connecting with someone · Handling requests · Booking a meeting · Messaging · The feed · Scoping catches people out · Troubleshooting · RelatedThe attendee directory, what Connect, Follow and Message each do, profiles, and booking a meeting with someone.
Inside: The directory · Connect, Follow, Message · The profile page · Booking a meeting · RelatedBuying, finding, showing and passing on a ticket — and what to do when something goes wrong.
Inside: Buying a ticket · Buying without an account · Free events · Finding your tickets · Showing your ticket at the door · Giving a ticket to someone else · Perks on a ticket · Troubleshooting · My ticket is not showing up · I paid but have no ticket · The QR will not scan · The app says my ticket is already used · I cancelled but was still charged · RelatedExample apps · 9 guides
Build the authentication example from scratch — connect to an organization, sign staff and customers in, answer verification codes, and watch every call the client makes.
Inside: Get the code · Before you start · Step 1 — The project · Step 2 — Hold the state · Step 3 — The request log · Step 4 — Connect to an organization · Step 5 — Sign somebody in · Step 6 — The verification sheet · Step 7 — The session · Step 8 — Run the whole thing · When it does not work · RelatedBuild the chat example from scratch — a customer signs in, opens a support conversation over the realtime gateway, waits in the queue, and talks to the agent who picks it up, with every socket event shown beside the thread.
Inside: Get the code · Before you start · Step 1 — The project · Step 2 — Credentials, state, two logs · Step 3 — Sign in as a customer · Step 4 — Wire the chat package to the client · Step 5 — Narrate the socket · Step 6 — The connection, where the person can see it · Step 7 — The thread · Step 8 — An agent to talk to · Step 9 — Run the whole thing · What the socket is actually doing · When it does not work · RelatedBuild the community example from scratch — a feed of posts written by customers, a comment thread, reactions that wait for the server, hashtags, and reporting.
Inside: Get the code · Before you start · Step 1 — The project · Step 2 — The community API · The feed · Posting · Comments · Reactions · Reporting · Step 3 — The feed page · Step 4 — The post card · Step 5 — The post page · Step 6 — Run the whole thing · When it does not work · RelatedBuild the CRM example from scratch — capture a lead without duplicating one, work it with actions the server records, look people up and read their journey, and text or call them through the organization's number.
Inside: Get the code · Before you start · Step 1 — The project · Step 2 — The CRM API · Leads · Actions · Contacts · Who the server thinks you are · The phone · Step 3 — Leads: the list and the duplicate check · Step 4 — Leads: one record and the actions · Step 5 — Contacts and journeys · Step 6 — Reaching somebody · Step 7 — The phone tab · Step 8 — What a browser cannot do · Step 9 — Run the whole thing · When it does not work · RelatedBuild the events example from scratch — create an event, add a ticket type, issue a ticket, and work the door with check-in, re-scan and check-out against a live server.
Inside: Get the code · Before you start · Step 1 — The project · Step 2 — Credentials and state · Step 3 — Sign in as staff · Step 4 — The events API · Creating an event · Ticket types · Tickets · The door · Step 5 — The events list · Step 6 — Ticket types and tickets · Step 7 — The door · Step 8 — Run the whole thing · What the numbers mean · When it does not work · RelatedBuild the payments example from scratch — open a tab, put items on it, and settle it one tender at a time: cash with change, a card with a reference, a split, a refund, and a receipt printed or sent — with every rule the server enforces shown in its own words.
Inside: Get the code · Before you start · Step 1 — The project · Step 2 — The POS API · A tab, and what goes on it · Money · Refunds · Receipts · Card present · Step 3 — The register · Step 4 — The tab · Step 5 — Taking payment · Step 6 — Where the browser stops · Step 7 — Run the whole thing · When it does not work · RelatedRun the actual Next.js example, trace its server transport and browser cart, and verify its boundaries before extending it.
Inside: Install and configure · Follow one catalog request · Follow one cart request · Understand what the cart stores · Verify and buildWorking apps built on AppEngine — a storefront, a sign-in, a till, a door scanner — each one a tutorial you can follow.
Inside: Which one to read first · What you need before any of them run · Getting the code · RelatedRun the Remix 2 example, trace loaders/actions, price a cart, and use its implemented reservation flow with current backend behavior.
Inside: 1. Run the checked-in project · 2. Keep upstream calls in server modules · 3. Trace cart pricing · 4. Read service definitions and availability · 5. Create one controlled booking · 6. Lookup and cancel: understand the actual contract · 7. Verify and buildGetting started · 4 guides
Organizations, datatypes, BaseModel, and the difference between a user and a customer.
Inside: 1. The organization is the tenant · 2. Everything is a datatype · 3. Every record is a BaseModel<T> · 4. Users and customers are different identities · 5. Roles gate content and components · NextThe vocabulary that shows up in Appmint source and these docs.
Sign in, read the token apart, and fetch records — with the exact payloads AppEngine returns.
Inside: 1. Check the server is up · 2. Sign in as a user · 3. Understand what the token is · 4. Make an authenticated request · 5. Read some data · 6. Refresh before it expires · Authenticating without a user · NextOne backend for commerce, CRM, operations and payments — and the products that run on it.
Inside: Start here · Products · Build with AI · For AI readers · Everything shares one backendHelp · 3 guides
Every how-to from Support › How do I…? in Studio Manager, written out step by step, with what happens at each step and where to read more.
Inside: Website · Build my website · Add another page to my site · Connect my domain · Selling · Add a product to sell · Take a payment / send an invoice · Handle an order that came in · Customers · Add or find a customer · Track people who have not bought yet · Messaging · Email or text my customers · Get a business phone number · Post to social media · Money & plan · Check my plan, credits and bills · Setup · Invite my team · Turn on AI · Set up my shop or office locationsEvery stop on the Studio Manager interface tour, written out — what each area is, when you would use it, and where to read more. The tour's "Learn more" links land here.
Inside: Chapter: Getting around · Welcome — let me show you the whole thing · The left menu is the product · Your dashboard, and Get started · App Root — the things that span everything · Inbox — everything people send you · Analytics · Chapter: Your website · Build Studio — where your website is made · New Web Page · Templates · Saved Pages · Manage Root Page · Domains · Chapter: Content & media · DAM — your content and files · Content Studio · Message Templates · Chapter: Selling · Storefront — what you sell · Products · Orders · Invoices · Inventory & shipping · Sales Channels · Chapter: Customers & messaging · CRM — the people side · Customers · Comm Center · Social Media · Leads · Forms · Chapter: AI & automation · AI, IVR and Automation · AI Assistant · Automation · IVR — your phone menu · Chapter: Money · Finance · Your plan and billing · Chapter: Your data · Database — your own data shapes · Import and export · Chapter: Setup & admin · Configuration · Users, groups and roles · Business locations · Phone & SMS · Setup Wizard · Chapter: When you get stuck · What's this? — point at anything · The AI agent · Help, how-tos and support · That's everythingEverything What's this? can explain in Studio Manager, one section each — the header controls, the dashboard card and every menu area and entry — with more detail than the pop-up card and links to the full pages.
Inside: The header · What's this? · Support · AI Agent · Phone · Live chat · Notifications · Language · Close all · Report a bug · Share workspace · The dashboard and the menu · Your dashboard, and Get started · The left menu · App Root · App Root · Inbox · Analytics · Domains · Setup Wizard · Build Studio · Build Studio · New Web Page · Templates · Saved Pages · Manage Root Page · DAM · DAM · Content Studio · Message Templates · Navigation · Storefront · Storefront · Products · Orders · Invoices · Inventory · Shipping · Returns · Sales Channels · CRM · CRM · Customers · Comm Center · Social Media · Leads · Forms · AI & automation · AI, IVR and Automation · AI Assistant · Automation · IVR · Money and account · Finance · Billing · Usage · Database · Database · Import, Export Data · Configuration · Configuration · User, Group · Role & Permission · Business Locations · Phone & SMSIntegrations · 3 guides
Every provider currently available, grouped by type, with what each is used for.
Inside: Social media · Payments · Marketplaces · Shipping and logistics · Messaging, email and voice · AI · Google and Microsoft · Databases · Other · Picking by use case rather than by name · RelatedThree provisioning models, automatic fallback to platform credentials, and bringing your own provider.
Inside: The three provisioning models · Shared · Sub-account · Bring your own · Automatic fallback · Isolation is preserved on fallback · Switching from ours to yours · Several configurations for one provider · What an integration must implement · Testing a connection · Calling an integration directly · RelatedConnected services, OAuth, webhooks and marketplace channels.
Inside: What connects · Connecting a service · Webhooks · Marketplace channels · Building your own · RelatedLeadSearch · 5 guides
How capture works on LinkedIn and Google Maps — and why the two behave differently.
Inside: LinkedIn · Google Maps · Where leads go · After capture · When a page will not capture · Staying within the rules · RelatedGet the extension, load it into Chrome, and connect it to your organization.
Inside: Getting it · Verify the download · Loading it into Chrome · Updating · Connecting it to your organization · Automatic — pick up an existing session · Manual — API key · Checking the connection · What it can access · NextA browser extension that captures B2B leads from LinkedIn and Google Maps straight into your CRM.
Inside: What it captures · How it works · Connecting it · After capture · Selector helper · Requirements · RelatedAuto-sync, default pipeline and stage, lead source, AI provider and notifications.
Inside: Auto-sync · Default pipeline and stage · Lead source · AI provider · Notifications · What is stored in the browser · RelatedConnection, capture and sync problems, in the order worth checking.
Inside: It says not connected · Credentials will not sync from Studio · Capture returns nothing · Captures are not appearing in the CRM · The side panel will not open · It stopped working after a Chrome update · Leads captured but I have lost them · Getting help · RelatedPlatform · 7 guides
Hire an AI employee, give it access, connect it to the system that runs it, confirm it is really running, give it work and answer what it asks — and what that system needs to know.
Inside: Before you start · Choose the runtime before hiring · Hire one · First exercise: create a draft project coordinator · Give it access · Make sure it is really running · Give it work and follow it · It keeps working on its own · The AI team workspace · Answer what it asks · For the system that runs it · Common problems · Phone and voice · Full course · RelatedWhat runs where, what each dependency is for, and how a request travels through AppEngine.
Inside: The backend process · Feature modules · The request pipeline · Data stores · Background work · Realtime · Resilience · The clientsBaseModel, the fields you get for free on every record, and how collections and subschemas work.
Inside: One envelope for everything · Keys · What every record gets for free · Lifecycle · Versioning and history · Row-level permissions · Engagement · Sharing · Publishing metadata · Styling · Schema definition · Collections · Query responsesAll 261 built-in datatypes, grouped by the part of the platform that owns them.
Inside: Core platform · HR, payroll and books · Storefront & commerce · Community & social · Identity & access · Events & ticketing · Stowbo — space custody · Investments & treasury · Chat & messaging · Logistics & delivery · Banking · Sites & domains · Automation · Affiliate & referral · Ledger & accounting · Lending · Dashboards & data viz · Benefits · Web analytics · Social publishing · AI employees · Workspace · Devices & hardwareUsers, customers, API keys and service accounts — and the exact order authorization is decided in.
Inside: Two kinds of identity · Credential types · Bearer token · Cookies · API key · Service account acting for a customer · Roles · Menu access · AI employees are users · How a request is authorized · Sign-in outcomes · Device binding and 2FA · Other sign-in paths · BlocklistsHow an orgid becomes a database, how domains resolve to tenants, and where the isolation boundary actually is.
Inside: Database per organization · Resolving the orgid · Routes exempt from the requirement · Domain-based tenancy · Platform-level orgs · Managing organizations · Scanner noiseAppMint as an identity provider. Register an app so its users sign in with their AppMint account over OpenID Connect or SAML 2.0, and use it to open hosted mailboxes in SpinForge webmail.
Inside: Who does what · Addresses to give an app · Register an app · OpenID Connect settings · SAML settings · Email the app receives · Who may sign in · Save, and copy the client secret · What people see when they sign in · Tokens and claims · Set up SpinForge webmail sign-in · For operators: production keys · RelatedStudio Manager · 23 guides
Profile, billing, API keys, usage and logs.
Inside: What lives here · API keys · Usage · Logs · RelatedAI assistants, phone menus, automations, workflow tasks and schedules.
Inside: Automation · Describing instead of building · Workflow · SLAs and escalation · Analytics · Schedules · RelatedInbox, analytics, dashboards, activity feed, domains, sites, services and the setup wizard.
Inside: What lives here · Inbox · Dashboards · Domains, sites and environments · Setup wizard · RelatedEvery method callable from data-action, data-source or the JavaScript API.
Inside: How to read this · cart — Storefront cart. · product — Catalog browse / search. · order — Customer orders. · storefront — Checkout, shipping, payments. · rental — Equipment / item rental. · customer — Authentication & customer dashboard. · ticket — Support tickets. · reservation — Bookings / reservations. · events — Public events. · repository — READ-ONLY generic data access. · media — Audio / video / animation. · ui — UI controls. · state — In-memory reactive store. · files — File management. · site — Site / org info. · page — Page lookup. · form — Form helpers. · contentPlayer — Posts played page by page (courses, applications, trainings). · Calling from a script · RelatedThe interactive web components a published page can use — tabs, accordions, dialogs, drawers, sliders, grids and mega menus.
Inside: The elements · Opening and closing · They hold live content · In design mode · Containers the panel recognizes · RelatedWhat runs after an action, and how bound values are rendered.
Inside: Effects · Worked example · Formats · Format options · RelatedBuild pages, forms, presentations and graphics — bound to live data — then publish.
Inside: Building a page · Forms · Responsive design · SEO and metadata · Publishing · The Build Studio dashboard · Graphic design · Templates · RelatedThe style slots on a page record, what executes and what does not, and the constraints that apply to code running inside a rendered page.
Inside: What executes, and what does not · It runs before the runtime exists · Constraints on code in this slot · Debugging · The Scripts library · RelatedThe data-* attributes that make a published page live — binding, lists, actions, visibility and formatting.
Inside: The full attribute set · Binding values · Lists · Where a path resolves · Actions · Triggers · Payload forms · Confirmation · Visibility · What you can reference · RelatedPages, feed, stories, connections, messages, groups, meetings, announcements, badges, hashtags and moderation.
Inside: What lives here · The feed · Connections and messaging · Moderation · Where community shows up · RelatedHost email for your own domain on SpinForge Mail, create mailboxes, give them to people and AI employees, and choose which ones the platform reads and sends from.
Inside: Before you start · Set up a domain · 1. Add the domain with SpinForge Mail as its provider · 2. Accept the agreement and claim the domain · 3. Prove you own the domain · 4. Publish the mail records · Create mailboxes · Remove email from a domain · Manage a mailbox from the accounts list · Let the platform read a mailbox · Sending as a mailbox · Give mailboxes to people and AI employees · AI employees and their mailbox · Your mailboxes, from the sidebar · RelatedLocations, users, groups, roles and permissions, password policy, integrations, escalation and translation.
Inside: What it covers · Users, groups and roles · Security settings · Locations · Integrations · Data transfers between organizations · Blacklist · RelatedLeads, pipelines, forms, campaigns, tickets, reservations, AI employees and a single view of every customer interaction.
Inside: What it covers · Leads · Where leads come from · The jobs, step by step · Forms · AI employees · Campaigns and audiences · Advertising · AI campaign generation · Reservations and appointments · Support tickets · Customer activity · The AI assistant · Communications · Affiliates · When something goes wrong · RelatedWrite single posts and multi-page documents — articles, courses, applications, trainings — set who can open them and in what order, preview, publish, and follow the people taking them.
Inside: The dashboard · Writing pages · Access & review — per page · Settings · Learners · Preview · Publishing · RelatedContent Studio (posts, multi-page documents and courses), categories, navigation, tags, comments, documents, site notices and message templates.
Inside: What it covers · Categories and tags · Navigation · View templates · Publishing and approval · Translation · RelatedCollections, sub-schemas, import and export, and the data explorer.
Inside: Base and custom collections · Schemas describe data and its editor · Sub-schemas · Import and export · Fixing a collection · RelatedEvents, sessions, ticket types, bookings, badge templates, speakers, exhibitors, check-ins and leads.
Inside: What lives here · Setting an event up · Bookings and tickets · Check-in · Leads · RelatedWallets, payouts, wallet transactions and payments.
Inside: What lives here · Wallets · Payouts · Payments · Customer-facing · RelatedDelivery zones, delivery agents and delivery jobs.
Inside: What lives here · Zones · Agents · Jobs · Carrier shipping is separate · RelatedThe console you sign in to — what each area does, and how the whole surface fits together.
Inside: The console at a glance · How navigation adapts · AI quick bars · Console header and help · Support menu · What's this? · Notifications · Close all · Report a bug · Share workspace · Language · Multi-location · Trash · The two halves · RelatedWhat an automation can do to a live call — speak, collect, transfer, record, pay and hand off to AI.
Inside: The actions · Variables · Collecting input · Payments on a call · Handing off to the AI · Webhooks · Choosing between the modes · RelatedGet a number, decide how calls are answered, and route them to the right people.
Inside: Getting a number · Buying one, step by step · Assigning numbers to staff · Outbound calling is a separate switch · Four ways to answer a call · Forwarding groups · Ring strategy · Targets · When nobody answers · Whisper and screening · Business hours · Voice and greetings · Recording and voicemail · Missed calls · The AI receptionist · Setting up the number · When something goes wrong · RelatedCatalog, cart, checkout, payments, orders, inventory, pricing, discounts, returns, rentals and point of sale.
Inside: What it covers · Catalog · Cart and checkout · Payments · Invoices, quotes and payment links · Orders · Point of sale · Inventory · Pricing · Discounts and gift cards · Returns · Rentals · Subscriptions · Tax and shipping · Selling elsewhere · RelatedVibe Studio · 2 guides
Visual AI app builder — describe what you want, then refine it visually against your real data.
Inside: How it works · Why it is not a mockup · Working with Vibe Agent · RelatedAn AI coding agent that builds against your own data, with multi-provider models, streaming and usage controls.
Inside: Multiple model providers · Prompt caching · Usage, rate limits and plans · Drop-in API compatibility · Streaming · RelatedWalkthroughs · 15 guides
Sign in as an operator, read a record, write a record — and the one header that makes reads fail in a way the error message does not explain.
Inside: Two kinds of sign-in · Sign in · The header that quietly breaks reads · A reusable client · Read something · Write something · Creating records · Checklist before moving onTake a folder of hand-written HTML to a live multi-page site — how pages are stored, a deploy script that is safe to re-run, the rewrites the platform expects, and how to verify a deploy without trusting status codes.
Inside: How a page is stored · The transforms · Inline the stylesheet · Rewrite internal links · Extract the metadata · The deploy script · Creating pages that do not exist yet · Page JavaScript · Verify the deploy · Status codes are not enough · Crawl your own links · Look at it · Things that bite · What the platform injects · Checklist · Where to go nextDefine a CRM form, open it to anonymous visitors, post to it from a page, and read the submissions back — including the permission that has to be set twice.
Inside: 1. Define the form · 2. The permission that has to be set twice · 3. Check it from outside · 4. Submit · 5. Wire it to a page · 6. Read submissions back · ChecklistConfigure a supported integration, test a provider operation, distinguish a custom API from a catalog provider, and verify email delivery.
Inside: 1. Configure a supported provider · 2. Exercise the provider in API Playground · 3. If the API is your own service · 4. Configure your business email account · 5. Troubleshoot the right layerChoose a portal layout, enable sections, save and verify the customer experience with separate identities.
Inside: 1. Prepare the website · 2. Open Client Portal · 3. Choose the layout · 4. Choose what customers see · 5. Check the actual customer experience · Try it yourselfName your site, choose a design or AI brief, create a page, customize it, preview it and prepare publishing.
Inside: 1. Start with the correct site · 2. Name your website · 3. Choose how to start · 4. Create the first page · 5. Make it yours · 6. Add the other pages and navigation · 7. Preview, publish and connect your domain · Your completion checklistA practical map from mobile sign-in to CRM, chat, calls, events, scanning, administration and hardware.
Inside: Prepare the phone or shared station · Customer and CRM work · Conversations, live chat and phones · Events: setup to final guest · Operational tools in the shared mobile app · Configure and support the app · Log a failed mobile check and continueEvery tutorial and example app, the three ways to reach the platform, and the setup every tutorial assumes.
Inside: Find the setup you need · Learn visually · Tutorials · Example apps · Three ways in · Which one for which job · What every tutorial assumes · A note on the responses in these pagesWhere page JavaScript actually goes — the page record's style field — when inline script tags run and when they don't, and the attribute bootstrap for when you only control the HTML.
Inside: The short version · The supported path: style.javascript · Writing it · Clearing it · When the <script> tag in your HTML runs · The attribute bootstrap: when you only control the HTML · Rules, if you use it · Do not split handlers from the payload · Make it idempotent either way · Verifying · When you need more than a page scriptUpload an image, generate favicon.ico and favicon.png from it, and wire both into the site record — the smallest complete task that touches files, a generator and a write.
Inside: 1. Prepare a square source · 2. Upload it · 3. Generate the favicons · 4. Patch the site record · 5. Page-level icon links are stripped · 6. Logos in CSS are a different story · VerifyEnable calling, acquire or connect a number, assign a user/group, configure routing and verify voice and SMS independently.
Inside: 1. Open Phone & SMS · 2. Prepare the service and outbound calling · 3. Get or connect the number · 4. Assign the number to an employee or team · 5. Decide where inbound calls go · 6. Register SMS separately · 7. Prepare the employee’s device · 8. Verify one complete call—and one messageDefine a bookable service, generate real availability, and create a reservation — from the server API and from a page, with a clear line between the endpoints that are public and the one that is not.
Inside: 1. Create a reservation definition · 2. Ask what is free · 3. Create the reservation · Which endpoints are public · 4. A booking widget with window.appmint · Verify against the backend · ChecklistCreate a chat configuration, embed it, make an agent available and verify a visitor-to-agent conversation.
Inside: 1. Prepare the site and agent · 2. Configure the widget · 3. Get the embed code · 4. Add it to the website · 5. Make an agent available · 6. Test both sides · Common problemsFrom signup to your first draft page: create your workspace, finish essential setup, find the builder and verify your first small win.
Inside: Your mission · 1. Sign up and reach your workspace · Walk through it · 2. Complete your first workspace setup · Walk through it · 3. Find your way around Studio Manager · Walk through it · 4. Shape one useful page · Walk through it · 5. Optional next step: meet Vibe Studio · Walk through it · 6. Your first win—and what comes next · Walk through it · Continue your setup · Keep exploringMeet Appmint Mobile through the jobs people actually do: customers, conversations, calls and events.
Inside: Your mission · 1. Make the phone yours · Walk through it · 2. Turn Home into a launchpad · Walk through it · 3. Know the customer before you reply · Walk through it · 4. Keep the conversation moving · Walk through it · 5. Welcome people through the event door · Walk through it · 6. Get ready for a real shift · Walk through it · Continue your setup · Keep exploring