docs
/
Courses — Appmint Mobile

Appmint Mobile Full Course: the app, every feature and its configuration

Watch on YouTube ↗

Video chapters
  1. 0:00 Welcome
  2. 0:22 How Appmint Mobile works
  3. 0:44 1 · Sign in to the right business: explained
  4. 0:57 1 · Sign in to the right business — email, business, password
  5. 1:24 2 · The tools on this phone: explained
  6. 1:40 2 · The tools on this phone — Device setup, layouts, group switches
  7. 2:30 3 · Location and devices: explained
  8. 2:47 3 · Location and devices — location, Business location settings, Devices
  9. 3:17 4 · Customer conversations: explained
  10. 3:30 4 · Customer conversations — Inbox, Jessica's order, reply by email
  11. 4:00 5 · Your tasks: explained
  12. 4:13 5 · Your tasks — Assigned to me, done in one tap
  13. 4:25 6 · Team requests and approvals: explained
  14. 4:39 6 · Team requests and approvals — Mike's time off, approved; team workspace
  15. 5:05 7 · The shared counter: explained
  16. 5:22 7 · The shared counter — passcode, handover note, Quick Sign-In at the counter
  17. 6:08 8 · The point of sale: explained
  18. 6:32 8 · The point of sale — POS settings, payment methods, Menu & 86 list
  19. 7:32 9 · Service: explained
  20. 7:56 9 · Service — reservations, arrivals, a table, the order sent to prep
  21. 8:45 9 · Service — the bar prep display
  22. 8:56 9 · Service — open checks, cash and the receipt
  23. 9:34 10 · CRM: explained
  24. 9:52 10 · CRM — Pipelines: a pickup order moves to Ready
  25. 10:08 10 · CRM — Leads: a catering lead qualified
  26. 10:26 10 · CRM — Contacts: find Brian, email him
  27. 10:42 10 · CRM — Support: reply, internal note, Done
  28. 11:16 11 · Talking with customers live: explained
  29. 11:35 11 · Live chat — the AI assistant hands Amanda to Emily
  30. 12:20 11 · Live Presence and Amanda's journey
  31. 12:32 11 · SMS and the phone
  32. 12:51 12 · Events: explained
  33. 13:14 12 · Events — workstation, setup, ticket sales, comps and the welcome desk
  34. 14:26 12 · Events — door scanning and access rules
  35. 14:48 12 · Events — venue, schedule, attendees and info center
  36. 15:21 13 · AI employees: explained
  37. 15:43 13 · AI employees — switch on, give work, pause
  38. 16:28 14 · Around the app: explained
  39. 16:45 14 · Around the app — Calendar, More, notifications and quick fixes
  40. 17:59 Wrap-up

Written guide

The written course is not yet available. The scope below is an outline.

  • Sign in: your email finds your business, then choose the organization; saved accounts and quick sign-in
  • Home and app groups: Comms, BusinessMade, CRM, Event, Workspaces & AI and System, shown by your role
  • The bottom bar: Dashboard, Inbox, Calendar, More and the Phone button
  • Configure the phone for a role: ready-made layouts (Front desk, Server, Prep, Cashier, event desks) or your own app groups; Reset
  • Business location, POS settings, menu and payment methods
  • Comms: business phone, live chat with AI handoff, SMS, the unified inbox and Live Presence
  • BusinessMade tools: POS, tabs, floor, reservations, arrivals, prep display and take payment
  • CRM: pipelines, tasks, contacts, leads, support tickets and meetings
  • Events: workstations, scanning, ticket sales, accreditation, schedule, people, stats, info and setup
  • Workspaces, AI employees and approvals
  • Shared devices: employee ID and passcode, staff cards and shift handover
  • Settings, notifications and troubleshooting
Appmint Mobile Home, device layouts and staff access — supporting guide

Prepare a phone for the operator's role and shift.

What you will learn

  • Sign in and select the organization
  • Choose a front-desk, server, prep, cashier or event device layout
  • Configure app groups for a field agent or mixed role
  • Return from focus view with All on; restore defaults with Reset
  • Assign the business location and distinguish layout from staff permissions
  • Use saved accounts, quick sign-in and staff cards

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

A device layout puts the right tools on Home for the person using it. Open Device setup on Home, or More → Features (apps & menus).

Choose a layout

LayoutWork it brings together
Restaurant — all toolsReservations, arrivals, floor, POS, tabs, prep, payments and devices
Front deskReservations, guest check-in, service points, tabs and phone
Server handheldFloor, POS, tabs and devices
Prep displayPrep stations and production stages
CashierTabs, POS, payment collection and devices
Event operationsAccreditation, ticket sales, scanning, schedules, participants and venue management
AccreditationsRegistration lookup, ticket pickup, walk-ins and participants
Ticket salesTicket desk, ticket types and attendee lookup
ScanningAdmission, exits, benefits and event information
Venue managementOccupancy, schedules, information, participants and event management

Choose a preset, then adjust individual app switches if the workstation combines jobs. For a field agent, enable the relevant CRM, communications and team apps. A prep workstation can serve food preparation, printing, assembly or another production process: the workflow and station names define the work.

Return to the full launcher

Open Features (apps & menus) and tap All on. This enables all apps available to your role and leaves the focused layout. You do not have to turn every switch on separately.

Reset returns to the default communications-focused selection. Group switches control entire sections; individual switches control apps within them. Your device layout is retained when staff sign out. Access still follows the current staff member's permissions.

POS settings

Open Features → POS settings or the POS settings action in the POS menu.

Prep controls

Show Send to prep controls whether the POS offers a separate preparation action. Keep it on when staff release selected items to production. Turn it off for a checkout-focused counter or self-service layout that does not need that operator action.

This is a device presentation setting. Configure any order fulfilment or production automation separately in the organization's workflows.

Payment choices

Enable the methods offered on this device: Cash, Tap to Pay, Card terminal (M2), Online card, Bank transfer and Other. Keep at least one method enabled. A method also needs the corresponding permissions, gateway and hardware before it can be used.

Give payment choices customer-friendly names, such as Card, Pay by card or a counter-specific label. The configuration keeps the technical method identity; the checkout displays the name you choose. A display name does not connect a terminal—use Connect card terminal to set up the hardware.

Business location

The location shown in the working screen's header is the device's assignment. Use its cog or More → Business location to open configuration. Business details and the card terminal belong under that location. See Business location and terminals.

Shared devices

Device layouts, staff identity and business permissions serve different purposes. Use a focused layout to simplify work, then configure staff access and quick sign-in according to your organization policy. See Shared devices.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Sign in and select the organization.
  2. Choose a front-desk, server, prep, cashier or event device layout.
  3. Configure app groups for a field agent or mixed role.
  4. Return from focus view with All on; restore defaults with Reset.
  5. Assign the business location and distinguish layout from staff permissions.
  6. Use saved accounts, quick sign-in and staff cards.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Business phone and staff softphone — supporting guide

Make and receive business calls using a staff-assigned number.

What you will learn

  • Assign a business number to a user or team
  • Allow microphone, notification and calling permissions
  • Check registration and select the From number
  • Use Keypad, Recent and Contacts
  • Receive calls and use mute, speaker and call controls
  • Manage online and offline status at shift changes

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Business softphone

The phone uses numbers assigned to your user or team. An administrator connects the business telephony service and assigns the number; you sign in as the intended employee and grant the required microphone, notification and calling permissions.

  1. Open Phone from Home or the phone control.
  2. Check registration and the device's online state.
  3. Select the available From number.
  4. Use Keypad, Recent or Contacts to place a call.
  5. Answer incoming calls and use the available mute, speaker and call controls.
  6. Set the phone offline when this device should stop receiving business calls, and online when the shift starts.

On Android, enable Appmint Mobile in calling-account settings if prompted. Native calling and background ringing depend on supported phone hardware, operating-system permissions and provider configuration; use supported phones for staff telephony.

Coordinate a customer handoff

Read the customer's existing history, answer in the appropriate channel, then record follow-up work in CRM. A field agent can combine Phone, Inbox, Contacts, Leads and Tasks on the same device. A support desk can combine Live Chat, Presence, Workspaces and Approvals.

See CRM, Team and AI and Device layouts.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Assign a business number to a user or team.
  2. Allow microphone, notification and calling permissions.
  3. Check registration and select the From number.
  4. Use Keypad, Recent and Contacts.
  5. Receive calls and use mute, speaker and call controls.
  6. Manage online and offline status at shift changes.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Live Chat and AI handoff — supporting guide

Take a website conversation from the waiting queue through human or AI resolution.

What you will learn

  • Set Available, Busy or Away and read connection status
  • Navigate Inbox, Queue, AI Chats, Customers and Agents
  • Take the next waiting visitor and read handoff context
  • Take over from AI, assist AI and resume AI
  • Send messages, photos and files
  • Transfer to another agent and close a completed conversation

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Live Chat

The agent console organizes real-time work into Inbox, Queue, AI Chats, Customers and Agents.

AreaUse
InboxWork conversations assigned to you
QueueReview waiting visitors and take the next conversation
AI ChatsFollow conversations handled by the assistant
CustomersSee online visitors and open their customer journey
AgentsSee colleagues and their availability

Check the connection indicator and set your status to Available, Busy or Away. Availability tells routing whether you can accept work. Use Pick Next for the next waiting visitor, then read the conversation and any AI handoff context before responding.

Human and AI collaboration

Takeover from AI moves a conversation to a staff member. Assist AI provides direction while the assistant is handling it. Resume AI returns the conversation to the assistant when appropriate.

Use Transfer Chat to hand the conversation to another agent, entering the correct staff email. Share the context needed for the handoff. End Chat closes a completed conversation after confirmation.

Attach a photo from the gallery, take a photo or select a file. The conversation identifies human, AI and system messages so staff can follow who said or changed what.

Live Presence and customer journey

More → Live Presence brings agents, visitors and the waiting queue together. Read availability, customer counts, waiting counts and handling figures. Refresh when reviewing current operational state.

Authorized supervisors can change an agent's status and manage queue entries. Open a customer's journey to review visits, orders, reservations, support, chats and calls before deciding the next action.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Set Available, Busy or Away and read connection status.
  2. Navigate Inbox, Queue, AI Chats, Customers and Agents.
  3. Take the next waiting visitor and read handoff context.
  4. Take over from AI, assist AI and resume AI.
  5. Send messages, photos and files.
  6. Transfer to another agent and close a completed conversation.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Business SMS conversations — supporting guide

Continue a customer's SMS conversation from the business number.

What you will learn

  • Configure a business sender and staff assignment
  • Find a customer conversation
  • Choose a recipient from contacts or enter the number
  • Compose and send the message
  • Read the conversation and delivery history
  • Continue the customer follow-up in CRM

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Unified inbox

The Communications screen offers Conversations and All Messages. Conversations group messages by contact and channel; All Messages provides a chronological message view. Use the channel chips to narrow the conversation list.

Open a conversation to read its history and load older messages. Reply in the conversation's channel. Email, SMS, WhatsApp, website and internal communication each retain their context. Internal notes are for staff; customer replies are delivered through the configured external channel.

New offers a new Email, SMS, WhatsApp or Internal message. Select or enter the recipient, add the subject where relevant, compose the message and send. Review the delivery result and history before following up.

SMS and other channels

SMS conversations use the organization's messaging numbers. Open a thread or compose a message with a recipient and body. Business-number assignment and SMS capability are configured by an administrator.

WhatsApp and other connected channels use their respective business integrations. Choose the intended recipient and channel before sending. The channel determines the available delivery features and sender identity.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Configure a business sender and staff assignment.
  2. Find a customer conversation.
  3. Choose a recipient from contacts or enter the number.
  4. Compose and send the message.
  5. Read the conversation and delivery history.
  6. Continue the customer follow-up in CRM.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Unified inbox, email and messaging — supporting guide

Read and answer customer messages in their original channel.

What you will learn

  • Navigate Conversations and All Messages
  • Filter conversation channels and load older messages
  • Reply in the existing channel
  • Compose email with recipients, subject, formatting and attachments
  • Start SMS, WhatsApp or internal messages
  • Find sent receipts and notifications in Communications Center and Message records

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Unified inbox

The Communications screen offers Conversations and All Messages. Conversations group messages by contact and channel; All Messages provides a chronological message view. Use the channel chips to narrow the conversation list.

Open a conversation to read its history and load older messages. Reply in the conversation's channel. Email, SMS, WhatsApp, website and internal communication each retain their context. Internal notes are for staff; customer replies are delivered through the configured external channel.

New offers a new Email, SMS, WhatsApp or Internal message. Select or enter the recipient, add the subject where relevant, compose the message and send. Review the delivery result and history before following up.

Email

Use the email composer for recipients, subject, a formatted message, links and attachments. Choose a contact with an email address when that is more convenient than typing. An existing conversation provides the context for a reply.

Email copies and delivery records are available in the platform's Message records and Communications Center. Use these records to find a receipt, reservation notice or customer reply without relying only on the recipient's mailbox.

SMS and other channels

SMS conversations use the organization's messaging numbers. Open a thread or compose a message with a recipient and body. Business-number assignment and SMS capability are configured by an administrator.

WhatsApp and other connected channels use their respective business integrations. Choose the intended recipient and channel before sending. The channel determines the available delivery features and sender identity.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Navigate Conversations and All Messages.
  2. Filter conversation channels and load older messages.
  3. Reply in the existing channel.
  4. Compose email with recipients, subject, formatting and attachments.
  5. Start SMS, WhatsApp or internal messages.
  6. Find sent receipts and notifications in Communications Center and Message records.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Live Presence and customer journey — supporting guide

See who is on the website and how staff are handling the queue.

What you will learn

  • Review agent availability and connected state
  • Read online visitors, queue and waiting figures
  • Open the customer journey before responding
  • Refresh the operational view
  • Use authorized status and queue controls
  • Coordinate a customer handoff with shared context

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Live Presence and customer journey

More → Live Presence brings agents, visitors and the waiting queue together. Read availability, customer counts, waiting counts and handling figures. Refresh when reviewing current operational state.

Authorized supervisors can change an agent's status and manage queue entries. Open a customer's journey to review visits, orders, reservations, support, chats and calls before deciding the next action.

Coordinate a customer handoff

Read the customer's existing history, answer in the appropriate channel, then record follow-up work in CRM. A field agent can combine Phone, Inbox, Contacts, Leads and Tasks on the same device. A support desk can combine Live Chat, Presence, Workspaces and Approvals.

See CRM, Team and AI and Device layouts.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Review agent availability and connected state.
  2. Read online visitors, queue and waiting figures.
  3. Open the customer journey before responding.
  4. Refresh the operational view.
  5. Use authorized status and queue controls.
  6. Coordinate a customer handoff with shared context.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile POS, product scanning and order entry — supporting guide

Build a sale and send selected items to preparation.

What you will learn

  • Confirm the assigned business location
  • Browse products, categories and day-parts
  • Use continuous camera scanning or an external BLE/HID scanner
  • Increase quantity with repeated product scans
  • Choose variations, modifiers, notes, course and seat
  • Use the phone cart summary and Review order
  • Save or update a tab and select items for Send to prep
  • Configure direct checkout, payment methods and payment display names

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Open POS from Home. The location beside the title identifies the workstation's business location. Use the configuration cog to manage that assignment.

Products and the cart

Search the catalogue, browse category and day-part filters, or scan a product. Product cards show the name and price. Choose a variation or modifiers when the item offers options, then add it to the order.

The phone layout keeps products and a cart summary on the same screen. The cart shows line quantities and a running total; Review order opens the detailed controls. On larger displays, the extra space supports a wider order view.

Change quantities with the line controls. Add line instructions, a seat or course where needed. Attach a customer so the order follows their account and service history. Menu availability and location pricing apply to the products you add.

Continuous product scanning

Tap Scan SKU to open the camera. Keep the scanner open while adding products; close it when finished. Present one product code at a time and move it away before scanning the next item.

A compatible external scanner can send codes directly into the active POS without focusing the search box. Scanning the same product again increases its quantity. Products with selectable options can require a choice before adding a line.

Use a product SKU, barcode or supported product QR code. Event tickets and reservation confirmations belong to their own scanning workflows. Scanner setup is covered in Devices.

Save and reopen a tab

Save a cart to keep an open bill for a customer, table, collection or job. Update saves changes to an existing tab. Open tabs lets you return to saved work; New starts a separate cart.

From Tabs, choose Open to continue an order or Settle to collect its outstanding balance. Fully paid orders are kept in the closed/payment history rather than offered as unpaid tabs.

Saved-tab tools include:

ToolUse
TransferMove the tab to another service point at the location
SplitDivide the bill into separate tabs, using the options offered for that order
PrintGive the customer a check before payment
Hide from this deviceRemove the tab from the local working list while retaining its saved record
Delete tab permanentlyRemove an eligible unused tab with no payments or fired work

Send selected items to prep

Select the unsent lines that should start now, add batch instructions, and choose Send to prep. Release another group later when it is ready for production. The app marks sent lines, and the workflow carries their quantities, options and notes to the appropriate stations.

A station can be a kitchen, bar, print room, assembly bench or other work area. Product workflow and station configuration determine routing. Open Prep for the station view or Pipelines for general workflow management.

In POS settings, turn Show Send to prep off when a checkout-focused workstation does not need a separate prep action. See Device layouts.

Checkout, tips and split payment

  1. Review the saved order and choose checkout or Settle.
  2. Review the order total, any amount already paid, and the balance due.
  3. Choose a tip preset or custom tip. The displayed amount includes the tip before payment starts.
  4. Select an enabled payment method and the amount for that portion.
  5. Use the payment action once, then follow the reader or phone's instructions.
  6. Continue with another tender until the balance is covered.

Cash, card-terminal, Tap to Pay, online-card, bank-transfer and other choices follow the device's payment settings and provider setup. Bank transfer and Other record an externally collected payment; use an appropriate reference. Cash can include change. Card and other non-cash portions must fit the remaining amount due.

For a connected card terminal, start payment from the checkout action, then tap or insert the card when prompted. Reader prompts describe the collection already in progress; they are not an instruction to begin another charge.

Resume a partially paid order

You can close checkout after one portion has been collected, reopen the same saved tab and pay the remaining balance. The summary separates Total, Paid and Due. Existing successful payments remain attached to the order and are not charged again.

For example, on a $16 order with $4 already paid in cash, reopening checkout shows $12 due. Collect the $12 using the next chosen method. Use a new cart for a separate sale rather than adding products to a completed payment.

Continue an interrupted payment

If collection was interrupted, reopen the order and inspect its payment state before starting another charge. Follow any pending-payment recovery offered by checkout. A payment-provider confirmation and recording that payment against the order are distinct steps; use the existing payment reference when recovering the same payment.

Receipts and reprints

After payment, choose Print, Email, SMS or the available receipt option. Enter the delivery details when needed. Printing or sending a receipt leaves the completion window open so you can review the result, send another copy or choose Close yourself.

A receipt is a record of a payment already taken. Reprinting does not take payment again. Use the saved order's receipt actions for another copy. Email and SMS delivery use the organization's messaging configuration and receipt templates.

Refunds

Open the paid order from Tabs → Closed, select a payment and use its refund action. Choose a full or partial refund within the refundable amount. A split payment has separate payment records; select the appropriate one for each refund. The original payment and refund remain in the order history.

Daily controls

Use More → Menu (day-parts & 86-list) to manage location availability. Mark an unavailable product off sale with a reason and restore it when available. Day-parts organize the catalogue for service periods.

Before a shift, check the business location, available payment methods, printer paper and scanner mode. For device setup, use Devices; for station work, use Prep and workflows.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Confirm the assigned business location.
  2. Browse products, categories and day-parts.
  3. Use continuous camera scanning or an external BLE/HID scanner.
  4. Increase quantity with repeated product scans.
  5. Choose variations, modifiers, notes, course and seat.
  6. Use the phone cart summary and Review order.
  7. Save or update a tab and select items for Send to prep.
  8. Configure direct checkout, payment methods and payment display names.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Tabs, split checks and order management — supporting guide

Reopen, move and split a customer's tab.

What you will learn

  • Find open, partial and closed tabs at the location
  • Open a saved bill in POS
  • Transfer the tab to another service point
  • Split a bill into separate checks
  • Print a check before payment
  • Reopen a partially paid order and read its remaining balance
  • Review receipts and refund individual payments
  • Start a new cart for a separate sale

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Tabs

The Tabs screen lists every bill at the location, grouped by section and card. Toggle Open and Closed at the top; filter with the chips:

ChipShows
AllEvery tab in the current view
OpenUnpaid, nothing paid yet
PartialSomething paid, balance outstanding
PaidFully paid
ReadyTabs with a fired item now marked ready
OverdueTabs with a fired item past its SLA

A card shows the label or table, the guest, item count, the subtotal and who has it. Open jumps into the POS with that tab active; Settle goes straight to checkout. Closed tabs are where refunds start.

The amount on a card is the subtotal

Tax and the final total are computed when the tab settles, so an open tab shows its running subtotal.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Find open, partial and closed tabs at the location.
  2. Open a saved bill in POS.
  3. Transfer the tab to another service point.
  4. Split a bill into separate checks.
  5. Print a check before payment.
  6. Reopen a partially paid order and read its remaining balance.
  7. Review receipts and refund individual payments.
  8. Start a new cart for a separate sale.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Checkout, tips, split payments and receipts — supporting guide

Collect tips and split payments, resume an outstanding balance and deliver the receipt.

What you will learn

  • Review Total, Paid and Due before collection
  • Set a tip preset or custom amount before paying
  • Choose enabled cash, card, terminal, bank or other tenders
  • Start card collection once and follow tap or insert prompts
  • Pay one portion, close checkout and reopen the same order
  • Collect the remaining balance without repeating successful payments
  • Continue a pending payment using its existing reference
  • Print, email or SMS the receipt and close the window explicitly
  • Refund an eligible payment or partial amount

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event. Configure the payment provider and compatible hardware used in the lesson before beginning collection or printing.

Checkout, tips and split payment

  1. Review the saved order and choose checkout or Settle.
  2. Review the order total, any amount already paid, and the balance due.
  3. Choose a tip preset or custom tip. The displayed amount includes the tip before payment starts.
  4. Select an enabled payment method and the amount for that portion.
  5. Use the payment action once, then follow the reader or phone's instructions.
  6. Continue with another tender until the balance is covered.

Cash, card-terminal, Tap to Pay, online-card, bank-transfer and other choices follow the device's payment settings and provider setup. Bank transfer and Other record an externally collected payment; use an appropriate reference. Cash can include change. Card and other non-cash portions must fit the remaining amount due.

For a connected card terminal, start payment from the checkout action, then tap or insert the card when prompted. Reader prompts describe the collection already in progress; they are not an instruction to begin another charge.

Resume a partially paid order

You can close checkout after one portion has been collected, reopen the same saved tab and pay the remaining balance. The summary separates Total, Paid and Due. Existing successful payments remain attached to the order and are not charged again.

For example, on a $16 order with $4 already paid in cash, reopening checkout shows $12 due. Collect the $12 using the next chosen method. Use a new cart for a separate sale rather than adding products to a completed payment.

Continue an interrupted payment

If collection was interrupted, reopen the order and inspect its payment state before starting another charge. Follow any pending-payment recovery offered by checkout. A payment-provider confirmation and recording that payment against the order are distinct steps; use the existing payment reference when recovering the same payment.

Receipts and reprints

After payment, choose Print, Email, SMS or the available receipt option. Enter the delivery details when needed. Printing or sending a receipt leaves the completion window open so you can review the result, send another copy or choose Close yourself.

A receipt is a record of a payment already taken. Reprinting does not take payment again. Use the saved order's receipt actions for another copy. Email and SMS delivery use the organization's messaging configuration and receipt templates.

Refunds

Open the paid order from Tabs → Closed, select a payment and use its refund action. Choose a full or partial refund within the refundable amount. A split payment has separate payment records; select the appropriate one for each refund. The original payment and refund remain in the order history.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Review Total, Paid and Due before collection.
  2. Set a tip preset or custom amount before paying.
  3. Choose enabled cash, card, terminal, bank or other tenders.
  4. Start card collection once and follow tap or insert prompts.
  5. Pay one portion, close checkout and reopen the same order.
  6. Collect the remaining balance without repeating successful payments.
  7. Continue a pending payment using its existing reference.
  8. Print, email or SMS the receipt and close the window explicitly.
  9. Refund an eligible payment or partial amount.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Floor and service-point management — supporting guide

Manage available and occupied tables or service points.

What you will learn

  • Read the assigned location and service-point types
  • Use grid and floor-plan views
  • Filter available, occupied, reserved, dirty and blocked points
  • Manage point details with the appropriate role
  • Seat a party and open its linked tab
  • Release, clear or block a service point
  • Keep seating state separate from payment state

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Floor

The Floor screen is the service-point map. Switch between the grid and the floor plan (an interactive canvas that places each point where an administrator positioned it; points with no position fall below the plan).

Filter by kind with the chips — seat, table, booth, bay, section, room, whatever your organization uses — and group by parent to see a section with its tables inside.

Colour is status:

StatusMeaning
AvailableFree to seat
OccupiedA party is seated; the card shows party size and how long
ReservedHeld for an upcoming booking
DirtyNeeds clearing before reuse
BlockedTaken out of service

Tap a point for its sheet: Open tab here starts a POS cart on that point, Block or Free up change status, Clear turns a dirty table available again. Long-press for the quick status actions. Changing status here never touches the tab or reservation linked to the point.

The jobs, step by step

Seat a walk-in. Check-in → Add walk-in → Name (required) with a Phone if you want to be able to text them, Party size, and any preference → Add to queue. When a table frees up, Assign on their card and pick the point. The dialog then offers Take order, which drops you into the POS on that table.

Take a booking over the phone. Reservations → the calendar icon → work the four steps below → Book. You will see Reservation created and the guest gets the confirmation.

Check in a guest who booked. Reservations → find them under Today → Check in. They join the live queue; seat them from Check-in exactly like a walk-in.

Check in a guest holding a confirmation code. Reservations → Scan reservation → point at the code on their phone or printout. A code that matches nothing reads No reservation matched "…"; one that matches but cannot be checked in reads Found but check-in failed — usually because they are already in the queue.

Bus a table. Floor (or Tables on Arrivals) → tap the point → Bus → mark dirty when the party leaves, then Cleaned — set available once it is wiped. Free up → available does both at once when there is nothing to clear.

Take a table out of service. Floor → tap the point → Block this spot. It stays out of the seating options until you free it.

Someone gave up waiting. Check-in → their card → Left. Use No-show instead when they had a booking and never came — that marks the booking, not just the queue.

Remove someone from the queue by mistake? Removal asks first: Remove from queue?

How a party moves

Booking → Check in on the Reservations screen → queue card on Check-in → Assign to a table → Take order into the POS on that table → Settle → release the table → clear it when bussed. Each step writes to the same records, so any device at the location sees the same state.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Read the assigned location and service-point types.
  2. Use grid and floor-plan views.
  3. Filter available, occupied, reserved, dirty and blocked points.
  4. Manage point details with the appropriate role.
  5. Seat a party and open its linked tab.
  6. Release, clear or block a service point.
  7. Keep seating state separate from payment state.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Reservations and service bookings — supporting guide

Create a reservation and follow it through the service queue.

What you will learn

  • Configure reservation definitions, services, hours and capacity
  • Book service type, service, date and available time
  • Record guest contact, party size and notes
  • Review Today, Upcoming and Past bookings
  • Find a reservation by guest or confirmation scan
  • Check the guest into arrivals or cancel the booking
  • Follow confirmation and cancellation messages

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Reservations

The Reservations screen is the booking book, grouped like the desktop counts them:

  • Today — bookings for today, plus walk-ins that have no start time.
  • Upcoming — future bookings, soonest first.
  • Past — folded away; tap Show to expand.

Each row shows party size, name, phone, the service, the date and time, and — once seated — the table name. Two actions:

Check in. Hands the party to the live queue. The row then shows In check-in queue with the time, and a second tap is refused, so a double tap cannot queue a party twice. Seating, notifying and no-shows happen on the Check-in screen from here.

Cancel. Cancels the booking and sends the cancellation notice.

Booking a reservation

The calendar icon opens a four-step wizard:

1. Service type. The reservation definitions your organization published (a consultation, a table service, a class).

2. Service and date. Pick a service if the definition offers several, then a date. A definition with no services configured books against itself with its default duration — you will see a note saying so rather than a dead end.

3. Time slot. Slots come from the server for that day, honouring work days, office hours and blocked time. Fully booked slots are disabled and show what is left.

4. Customer. Name and phone are required; email, party size and notes are optional. Book creates the reservation and sends the confirmation.

The jobs, step by step

Seat a walk-in. Check-in → Add walk-in → Name (required) with a Phone if you want to be able to text them, Party size, and any preference → Add to queue. When a table frees up, Assign on their card and pick the point. The dialog then offers Take order, which drops you into the POS on that table.

Take a booking over the phone. Reservations → the calendar icon → work the four steps below → Book. You will see Reservation created and the guest gets the confirmation.

Check in a guest who booked. Reservations → find them under Today → Check in. They join the live queue; seat them from Check-in exactly like a walk-in.

Check in a guest holding a confirmation code. Reservations → Scan reservation → point at the code on their phone or printout. A code that matches nothing reads No reservation matched "…"; one that matches but cannot be checked in reads Found but check-in failed — usually because they are already in the queue.

Bus a table. Floor (or Tables on Arrivals) → tap the point → Bus → mark dirty when the party leaves, then Cleaned — set available once it is wiped. Free up → available does both at once when there is nothing to clear.

Take a table out of service. Floor → tap the point → Block this spot. It stays out of the seating options until you free it.

Someone gave up waiting. Check-in → their card → Left. Use No-show instead when they had a booking and never came — that marks the booking, not just the queue.

Remove someone from the queue by mistake? Removal asks first: Remove from queue?

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Configure reservation definitions, services, hours and capacity.
  2. Book service type, service, date and available time.
  3. Record guest contact, party size and notes.
  4. Review Today, Upcoming and Past bookings.
  5. Find a reservation by guest or confirmation scan.
  6. Check the guest into arrivals or cancel the booking.
  7. Follow confirmation and cancellation messages.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Arrivals, walk-ins and service assignment — supporting guide

Check in a guest and assign an available service point.

What you will learn

  • Read the Waiting, Bookings, Tables and History views
  • Add a walk-in with party and contact details
  • Check in a booked guest
  • Read queue counts, wait times and preferences
  • Notify and assign an available service point
  • Open the seated party’s order
  • Manage left, no-show and service-point release actions

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Check-in and Arrivals

Use the Waiting, Bookings, Tables and History tabs to move between the active queue, expected guests, service points and recent activity. Add walk-in and New booking start the two arrival paths.

The Check-in screen is the live queue for this location. The top strip shows people in queue, average wait and the longest current wait.

Queue cards show the party, size, source (walk-in or reserved), how long they have waited, any preferences, and four actions:

ActionWhat happens
NotifyRe-sends the "your table is ready" email and SMS
AssignPick a free service point. The point becomes occupied, the booking is marked used, the guest is notified, and a dialog offers Take order, which opens the POS on that table
LeftThe party gave up; the queue entry closes, the booking is untouched
No-showCloses the entry and marks the booking no-show

Add walk-in adds a party with name, phone or email (at least one), party size, preferences and a preferred point. The guest gets a place in the queue and a record in the CRM.

Tables shows service points and occupants; open a point to manage its availability. Bookings shows expected guests and History shows recent check-in activity.

Assign refuses an occupied or reserved point

The server will not seat a party onto a point whose status is occupied or reserved. Clear it first, or pick another.

The jobs, step by step

Seat a walk-in. Check-in → Add walk-in → Name (required) with a Phone if you want to be able to text them, Party size, and any preference → Add to queue. When a table frees up, Assign on their card and pick the point. The dialog then offers Take order, which drops you into the POS on that table.

Take a booking over the phone. Reservations → the calendar icon → work the four steps below → Book. You will see Reservation created and the guest gets the confirmation.

Check in a guest who booked. Reservations → find them under Today → Check in. They join the live queue; seat them from Check-in exactly like a walk-in.

Check in a guest holding a confirmation code. Reservations → Scan reservation → point at the code on their phone or printout. A code that matches nothing reads No reservation matched "…"; one that matches but cannot be checked in reads Found but check-in failed — usually because they are already in the queue.

Bus a table. Floor (or Tables on Arrivals) → tap the point → Bus → mark dirty when the party leaves, then Cleaned — set available once it is wiped. Free up → available does both at once when there is nothing to clear.

Take a table out of service. Floor → tap the point → Block this spot. It stays out of the seating options until you free it.

Someone gave up waiting. Check-in → their card → Left. Use No-show instead when they had a booking and never came — that marks the booking, not just the queue.

Remove someone from the queue by mistake? Removal asks first: Remove from queue?

How a party moves

Booking → Check in on the Reservations screen → queue card on Check-in → Assign to a table → Take order into the POS on that table → Settle → release the table → clear it when bussed. Each step writes to the same records, so any device at the location sees the same state.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Read the Waiting, Bookings, Tables and History views.
  2. Add a walk-in with party and contact details.
  3. Check in a booked guest.
  4. Read queue counts, wait times and preferences.
  5. Notify and assign an available service point.
  6. Open the seated party’s order.
  7. Manage left, no-show and service-point release actions.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Standalone payment collection — supporting guide

Collect a configured payment from the mobile payment screen.

What you will learn

  • Confirm the business location
  • Enter a service fee, deposit or quick-sale amount and description
  • Review the created order at checkout
  • Collect payment using the configured method
  • Apply tips and split tenders as needed
  • Resume an open or partially paid quick sale
  • Deliver a receipt and locate the payment for follow-up

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event. Configure the payment provider and compatible hardware used in the lesson before beginning collection or printing.

Take payment is for money that does not start as an order: a deposit, a callout fee, a balance someone owes, a phone sale you are not going to build line by line. Open it from the home tile.

What it does

1. Enter an amount and a description. The description becomes the tab's label, so it is what you will see later in the Tabs list and on the receipt. Leave it blank and the tab is called "Quick sale".

2. Continue. The app opens a tab at the current location with a single QUICK-SALE line for that amount, saves it, and hands you to the normal checkout.

3. Take the money. Cash, Tap to Pay, the M2 reader, a bank transfer or "other" — every tender, tip and receipt option you have on a tab is here too.

That design is deliberate. A quick charge is a real order with a real number, so it shows in reporting, posts to the ledger and can be refunded, exactly like a sale rung up item by item.

Taking the money, method by method

Checkout is the same screen a tab settles through, so these steps apply to both.

Cash. Set the method to Cash, type what they handed you in Cash tendered (optional), and the change due appears under the tender. Leave it blank and the full amount is simply recorded as paid. A cash settle also kicks a drawer wired to the receipt printer.

Card in person. Set the method to Tap to Pay or Card — whichever this device has — and use the checkout payment action. Follow the prompt on the reader or the phone's Tap to Pay sheet. If no reader is paired the screen says No M2 reader paired. Pair one in Devices first. with a Connect card terminal action.

Card taken over the phone. Use Card (online) and enter the card details in the Stripe sheet.

Bank transfer or something else. Bank transfer or Other record the money against the tab with a reference. Nothing is charged — use these only once the money has actually arrived.

Splitting across methods. Add tender (split bill) adds a second row; give each one its own amount and method. Each row charges on its own, so a card that declines does not undo cash already taken — the tab simply shows PARTIAL · $x due until the rest is covered.

Tips. Pick a percentage or Custom, before charging. The tip lands on the first tender that has not been charged yet.

Receipt. Once the balance is covered, choose Print, Email, SMS or None. Printing or sending leaves the window open until you choose Close. Email and SMS ask for the address or number; Enter an email address first. means you tapped send with the field empty.

Where it goes

Tabs screenThe charge appears as a tab named after the description, paid once you finish
ReportingCounted as a sale at the location, line QUICK-SALE
ReceiptPrint, email or SMS, on the organization's receipt template
RefundFrom the closed tab, like any payment

If you stop halfway

The tab is created before you are asked for money. Back out of checkout and you leave an open tab with a single quick-sale line and nothing paid. That is not lost money — it is an unpaid bill.

Find it on the Tabs screen (filter Open) and either settle it or delete it. Do not start a second charge for the same thing without checking, or the customer will be asked to pay twice.

Tax follows the location's rules

The quick-sale line is a fee line, so whether tax is added depends on how fees are configured for the location. The checkout total shows what will be charged before you take a tender.

When something goes wrong

What you seeWhat it meansWhat to do
Enter an amountContinue was tapped with no amountType the amount first; the button shows the figure it will charge.
Failed to start chargeThe tab could not be opened on the serverCheck the connection and the location, then try again. Nothing has been charged.
No M2 reader paired. Pair one in Devices first.Card-present chosen with no reader on this devicePair now, or take the money another way.
Card declinedThe bank refused itAsk for another card, or take cash. The tender stays uncharged — nothing was taken.
Stripe is not configured. Add a StripeProvider integration.The organization has no card processing set upRecord another tender; an administrator adds Stripe on the web.
Failed to create Stripe payment intent.The charge could not be started with StripeRetry once. If it repeats, take another tender and check the Stripe integration.
Server accepted the request but didn't confirmThe payment may have gone throughDo not charge again. Check the tab's payment list first, and the Stripe dashboard if unsure.
Server returned no receipt payload.Paid, but no receipt renderedThe money is taken. Re-send the receipt from the tab.
Print failed: …Printer off, out of range, or unpairedCheck it under More → Printer; email or text the receipt meanwhile.
Drawer kick skipped: …The drawer could not be openedOpen it with the key. Check the drawer cable at the printer.
An unpaid quick sale is sitting on the Tabs listYou backed out of checkoutSettle it or delete it — see If you stop halfway above.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Confirm the business location.
  2. Enter a service fee, deposit or quick-sale amount and description.
  3. Review the created order at checkout.
  4. Collect payment using the configured method.
  5. Apply tips and split tenders as needed.
  6. Resume an open or partially paid quick sale.
  7. Deliver a receipt and locate the payment for follow-up.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Prep, production and workflow management — supporting guide

Route and progress prep, production and service work through configured stations and stages.

What you will learn

  • Choose a prep, print-production, assembly or service workflow
  • Route product work to configured stations
  • Send selected order lines with batch instructions
  • Filter stations and read quantities, options and deadlines
  • Advance stages or mark work complete
  • Add notes, snooze, escalate, reassign or cancel tasks
  • Review readiness and overdue indicators from the order
  • Use the operations dashboard for supervisory follow-up

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Prep provides a focused station view, while Pipelines opens general workflow tasks. Send to prep routes selected unsent order lines into their configured workflow. Use stations for food preparation, printing, assembly, pickup, service appointments or other production work. The workflow supplies the stages and actions; it is not limited to restaurant service.

Picking a workflow

Choose Prep display in Device setup for a dedicated production workstation. Set the workflow and station once, then use that view through the shift. Front-desk, server and cashier devices can keep their own layouts while working the same order records.

A print shop might use Received → Artwork review → Printing → Finishing → Ready; an assembly area might use Received → Assembly → Inspection → Dispatch. Configure those stages centrally, then work them on mobile.

The dropdown at the top lists the workflow definitions in your organization. Orders fire into prep-pipeline by default, whose stages are:

StageMeaning
ReceivedThe ticket has arrived at the station
PreppingSomeone has started it
ReadyDone — the tab shows a Ready chip on the Tabs screen
DeliveredTaken to the guest

Other workflows have their own stages; the screen shows whatever the definition says.

Nothing to pick?

The dropdown only lists workflows that exist in the organization. They are created automatically the first time something uses them — the prep pipeline appears after the first fire, the check-in pipeline after the first walk-in.

What a task shows

Each card is one fired ticket. Its title is chosen in this order: the tab's label, then the service point, then the order number, then the first product — so a ticket reads "Patio 4" or "T7" rather than an internal id when the tab has a name.

Under the title: the lines with quantities and their modifiers, course and seat if set, special instructions, how long since it was fired, and the SLA state. A task past its due time is marked overdue and the tab it belongs to shows Overdue on the Tabs screen.

Tasks are listed in every working status — new, pending, in progress and blocked — plus what was finished in the last 24 hours, so a station can see what just went out.

Stations

If fired lines carry a prep station (kitchen, bar, barista — set on the product), a chip row appears. Pick a station and the list shows only tickets with lines for it. The All view is the pass. A ticket that spans two stations shows under both.

Working a ticket

ActionWhat it does
AdvanceMove to the next stage
Mark doneComplete it outright
Add noteA note visible on the task's history
SnoozeHide it for a while without losing it
EscalateEscalate now rather than waiting for the SLA to breach
ReassignHand it to another person or station
CancelDrop the ticket; the order line stays on the tab

Advancing to Ready is what flips the tab's chip. Delivering it clears the chip.

Snooze asks how long: pick a preset or Custom (minutes). It pauses the SLA timers for that task, so a ticket waiting on the guest does not go overdue for a reason nobody controls.

Escalate confirms first — Escalate this task to the next tier now? — and pushes it to the next tier immediately rather than waiting for the SLA to breach.

Reassign takes comma-separated emails, and the list you type replaces the current assignees rather than adding to them. Include everyone who should still be on it.

Cancel task drops the ticket. The order line stays on the tab, so the guest is still charged for it unless you also remove the line in the POS.

Refires and duplicates

Firing is idempotent. Lines that already have a ticket are skipped, and if every line on a tab has been fired the server answers "All requested items are already fired". For additional production, add the intended new work and send it as a new batch.

The manager view

The Operations dashboard (reached from the operations screens' overflow) polls wait times and escalations every 30 seconds: average and longest waits per stage, tickets that have breached their SLA and those about to. It is separate from the ticket list so its polling does not redraw the screens staff are working on.

When something goes wrong

What you seeWhat it meansWhat to do
No workflows configuredThe organization has no workflow definitions yetThey appear on first use — fire something from the POS, or create one in the admin under Workflows.
Pick a workflow and nothing loadsNo workflow is selectedChoose one from the dropdown at the top.
No active tasks in this workflowNothing is in flightExpected between rushes. Tickets appear when items are fired from the POS.
No tickets for this stationThe station filter is on and has nothingSwitch to All stations to see the pass.
A fired item never appearedIts product has no prep station, or you are filtered to another stationCheck All stations; set the product's station under menu and stock.
All requested items are already fired back at the POSEverything on the tab has a ticketAdd a new line and fire that — firing does not duplicate.
A ticket stays overdue after the guest was servedIt was never advanced past ReadyAdvance to Delivered, or Mark done.
Reassigning lost the previous ownerThe email list replaces the assigneesReassign again with every address that should be on it.
A cancelled ticket is still on the billCancelling the task does not touch the orderRemove the line in the POS if it should not be charged.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Choose a prep, print-production, assembly or service workflow.
  2. Route product work to configured stations.
  3. Send selected order lines with batch instructions.
  4. Filter stations and read quantities, options and deadlines.
  5. Advance stages or mark work complete.
  6. Add notes, snooze, escalate, reassign or cancel tasks.
  7. Review readiness and overdue indicators from the order.
  8. Use the operations dashboard for supervisory follow-up.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Tasks and field follow-up — supporting guide

Create and maintain assigned work on the phone.

What you will learn

  • Open and filter the task list
  • Create a task with clear context
  • Set due date, status and assignees
  • Update progress and completion
  • Connect the follow-up to customer work
  • Distinguish ordinary tasks from staged workflow work

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Tasks

Use Tasks for ordinary assigned work: title, description, due date, assignees and status. Create a task, update the details and mark progress as the work is completed. A task is useful for a callback, site visit or follow-up after a sale.

Use Pipelines for work that moves through configured stages, assignments and service deadlines. Prep tasks belong to those workflows rather than the ordinary task list.

A field-agent routine

  1. Open the assigned lead or find the contact before a visit.
  2. Read the customer journey and previous communication.
  3. Call or message through the business channel.
  4. Update the lead and capture the agreed next step.
  5. Create a task or meeting for follow-up.
  6. Use the relevant workflow for work handed to another team.

Continue with Communications, Prep and workflows and Workspaces.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Open and filter the task list.
  2. Create a task with clear context.
  3. Set due date, status and assignees.
  4. Update progress and completion.
  5. Connect the follow-up to customer work.
  6. Distinguish ordinary tasks from staged workflow work.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Contacts and customer context — supporting guide

Find a customer's record and continue the relationship.

What you will learn

  • Browse All, Appmint and Device contacts
  • Search before creating duplicate customer records
  • Open contact details and business context
  • Call, SMS, email or schedule a meeting
  • Read the customer journey
  • Maintain customer master details through the CRM workspace

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Contacts

Browse All, Appmint and Device contacts. Appmint contacts provide business records; Device contacts use the phone's address book with permission. Search by name, email or company and open a record to read its details.

Use the contact's communication actions for a call, SMS, email or meeting. Business calls and messages follow the configured business-number and channel setup. Maintain customer master details through the web CRM where appropriate, then use the same record for mobile follow-up.

Customer journey

Open the journey from customer context to see the relationship across visits, orders, bookings, support, chats and calls. Use its summary and timeline to understand what has already happened before contacting the person again.

Authorized data-management actions should follow the organization's customer-data policy. They are separate from routine sales or service follow-up.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Browse All, Appmint and Device contacts.
  2. Search before creating duplicate customer records.
  3. Open contact details and business context.
  4. Call, SMS, email or schedule a meeting.
  5. Read the customer journey.
  6. Maintain customer master details through the CRM workspace.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Lead capture, qualification and follow-up — supporting guide

Capture and update a lead with source and sales context.

What you will learn

  • Search and filter leads by status
  • Capture name, company, contact details and source
  • Read value, priority, score, owner and pipeline stage
  • Qualify, disqualify and update lead details
  • Assign a colleague and schedule follow-up
  • Convert a qualified lead through the customer workflow
  • Record event and field context for the next conversation

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Leads

Search leads and filter by status. A lead row shows its identity, company, status, value and assignment. Open it for contact details, source, score, priority, pipeline, stage and activity history.

Use the add action to capture a lead's name, email, phone, company and initial status. On the detail screen, maintain the available fields, qualify or disqualify the lead, assign an owner and schedule follow-up. Conversion connects a qualified lead with customer and sales records according to the chosen flow.

At an event or site visit, record enough context to make follow-up useful: where you met, what the person needs and the next agreed action. Search before adding to keep the relationship in one record.

Customer journey

Open the journey from customer context to see the relationship across visits, orders, bookings, support, chats and calls. Use its summary and timeline to understand what has already happened before contacting the person again.

Authorized data-management actions should follow the organization's customer-data policy. They are separate from routine sales or service follow-up.

A field-agent routine

  1. Open the assigned lead or find the contact before a visit.
  2. Read the customer journey and previous communication.
  3. Call or message through the business channel.
  4. Update the lead and capture the agreed next step.
  5. Create a task or meeting for follow-up.
  6. Use the relevant workflow for work handed to another team.

Continue with Communications, Prep and workflows and Workspaces.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Search and filter leads by status.
  2. Capture name, company, contact details and source.
  3. Read value, priority, score, owner and pipeline stage.
  4. Qualify, disqualify and update lead details.
  5. Assign a colleague and schedule follow-up.
  6. Convert a qualified lead through the customer workflow.
  7. Record event and field context for the next conversation.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Support tickets and customer follow-up — supporting guide

Record and follow customer support work.

What you will learn

  • Find the customer’s existing issue
  • Create a support ticket with issue context
  • Choose priority, severity, status and channel
  • Assign responsibility and maintain the available fields
  • Coordinate customer replies through the appropriate channel
  • Follow the ticket through resolution

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Support tickets

Use Support to record and track a customer issue. Create a ticket with its title, description, customer context, priority, severity and channel. Maintain its status and assignment using the actions available to your role.

Keep customer-facing communication in the appropriate message channel and internal handling context with the team's work records. Use the web support workspace for broader service administration and coordinated customer replies.

Tasks

Use Tasks for ordinary assigned work: title, description, due date, assignees and status. Create a task, update the details and mark progress as the work is completed. A task is useful for a callback, site visit or follow-up after a sale.

Use Pipelines for work that moves through configured stages, assignments and service deadlines. Prep tasks belong to those workflows rather than the ordinary task list.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Find the customer’s existing issue.
  2. Create a support ticket with issue context.
  3. Choose priority, severity, status and channel.
  4. Assign responsibility and maintain the available fields.
  5. Coordinate customer replies through the appropriate channel.
  6. Follow the ticket through resolution.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Event workstations and staff navigation — supporting guide

Select the correct event before running staff operations.

What you will learn

  • Choose Event operations or a dedicated event layout
  • Select the active event
  • Navigate Overview, Scanner, Tickets, Schedule, People and More
  • Assign a scan point or accreditation desk
  • Coordinate ticket sales, admission and venue management
  • Return to the broader app launcher with All on

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Appmint Mobile gives event staff a shared workspace for the ticket desk, entrances, benefit counters and venue operations. Attendees use their ticket confirmation, printed ticket or EventOxygen ticket while staff work in the selected event.

Set up an event workstation

Choose an event layout under Device setup: Event operations, Accreditations, Ticket sales, Scanning or Venue management. Open Events and select the event before beginning work. The event name stays visible in the event workspace.

The event workspace provides Overview, Scanner, Tickets, Schedule, People and More. Home shortcuts also provide access to event information, statistics, accreditation and management according to the device layout and staff role.

To use other business apps, open More → Features (apps & menus) → All on. Changing the layout does not remove the organization's other modules.

Set the scan point

Open Scanner and use its settings cog to select the scan point, such as Main Gate, West Exit, VIP Entrance or Lunch Desk. The scan point supplies the zone and operating rules. General entry/exit can use a selected zone where the event does not assign a named point.

Configure event zones, capacities, scan points, accreditation desks, ticket types and benefits in the event's administrative setup. Staff select the configured station on the device rather than recreating the event's rules at each door.

Entry and continuous scanning

  1. Select Entry at the correct event and scan point.
  2. Present the ticket QR code to the camera or use a compatible external scanner.
  3. Read the result before admitting the holder.
  4. Present the next ticket. The scanner stays ready without an additional “next person” button.

A successful result records admission. Not allowed explains a refusal, such as a cancelled ticket, a ticket for another event, restricted zone access, a duplicate entry, exhausted re-entry allowance or a full zone. Staff should follow the displayed decision. Reading a barcode or feeling a vibration is not itself admission approval.

The result card has a dismiss control. Leaving it visible does not require the next guest to wait for a separate confirmation tap. Repeated camera frames are suppressed so holding one QR in view does not create repeated admissions.

Exit and re-entry

Switch to Exit at the appropriate point and scan the ticket as the holder leaves. Exit updates movement history and the zone's current occupancy.

A return is a new Entry scan. Re-entry follows the ticket type's policy, the previous exit and any time or access rules. The re-entry allowance counts additional admissions after the first entry: an allowance of 1 permits the original entry and one return after exit. It does not count the original entry as that return.

A repeat Entry while the holder is still inside is not a valid exit-and-return sequence. Scan an actual departure in Exit mode so both admission rules and capacity remain accurate.

Capacity and zone access

Zones can have their own capacities and ticket-type access. Entry to a full zone is refused until an exit frees capacity. A holder eligible for the event is not automatically eligible for every restricted zone.

Use the assigned zone consistently at entry and exit. The venue dashboard distinguishes current occupancy from cumulative attendance. See Venue operations.

Benefits and entitlements

Use Benefits at a configured benefit point, such as lunch collection, merchandise pickup or a VIP service. Scan the ticket to check that it includes the relevant benefit, is within the permitted conditions and has uses remaining.

The result records an allowed redemption. A second presentation cannot redeem a one-use benefit again. Benefits governed by event presence require the holder to be inside; an exited holder must complete an allowed re-entry before redeeming. A benefit scan does not itself admit the holder or override an entry refusal.

For setup and examples, see Re-entry and benefits.

Ticket lookup

Use Ticket lookup when a code cannot be read. Enter the ticket code or holder email, then choose the correct ticket if several match. Lookup follows the current event, scan point and Entry, Exit or Benefits mode. The same admission and entitlement rules apply.

Keep the ticket's identity and event visible while resolving a guest enquiry. Use accreditation lookup for booking and collection work rather than repeatedly attempting entry.

Sales and accreditation

The Tickets area supports selling, issuing and complimentary tickets. Accreditation Desk handles registration lookup, ticket collection, walk-ins and ticket printing. Ticket checkout can collect payment and print admission QR codes with a receipt.

See Ticket sales and accreditation for the complete desk workflow, and Venue operations for schedules, participants and oversight.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Choose Event operations or a dedicated event layout.
  2. Select the active event.
  3. Navigate Overview, Scanner, Tickets, Schedule, People and More.
  4. Assign a scan point or accreditation desk.
  5. Coordinate ticket sales, admission and venue management.
  6. Return to the broader app launcher with All on.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Continuous ticket scanning, entry and exit — supporting guide

Check attendees in and out while recording their zone.

What you will learn

  • Configure event, scan point and zone
  • Use continuous camera or external-scanner input
  • Record Entry and read allowed or refused results
  • Move to the next holder without another confirmation tap
  • Use the result’s dismiss control
  • Record Exit and apply re-entry allowances correctly
  • Apply duplicate, cancelled, wrong-event, zone and capacity rules
  • Use Ticket lookup by code or email

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Appmint Mobile gives event staff a shared workspace for the ticket desk, entrances, benefit counters and venue operations. Attendees use their ticket confirmation, printed ticket or EventOxygen ticket while staff work in the selected event.

Set up an event workstation

Choose an event layout under Device setup: Event operations, Accreditations, Ticket sales, Scanning or Venue management. Open Events and select the event before beginning work. The event name stays visible in the event workspace.

The event workspace provides Overview, Scanner, Tickets, Schedule, People and More. Home shortcuts also provide access to event information, statistics, accreditation and management according to the device layout and staff role.

To use other business apps, open More → Features (apps & menus) → All on. Changing the layout does not remove the organization's other modules.

Set the scan point

Open Scanner and use its settings cog to select the scan point, such as Main Gate, West Exit, VIP Entrance or Lunch Desk. The scan point supplies the zone and operating rules. General entry/exit can use a selected zone where the event does not assign a named point.

Configure event zones, capacities, scan points, accreditation desks, ticket types and benefits in the event's administrative setup. Staff select the configured station on the device rather than recreating the event's rules at each door.

Entry and continuous scanning

  1. Select Entry at the correct event and scan point.
  2. Present the ticket QR code to the camera or use a compatible external scanner.
  3. Read the result before admitting the holder.
  4. Present the next ticket. The scanner stays ready without an additional “next person” button.

A successful result records admission. Not allowed explains a refusal, such as a cancelled ticket, a ticket for another event, restricted zone access, a duplicate entry, exhausted re-entry allowance or a full zone. Staff should follow the displayed decision. Reading a barcode or feeling a vibration is not itself admission approval.

The result card has a dismiss control. Leaving it visible does not require the next guest to wait for a separate confirmation tap. Repeated camera frames are suppressed so holding one QR in view does not create repeated admissions.

Exit and re-entry

Switch to Exit at the appropriate point and scan the ticket as the holder leaves. Exit updates movement history and the zone's current occupancy.

A return is a new Entry scan. Re-entry follows the ticket type's policy, the previous exit and any time or access rules. The re-entry allowance counts additional admissions after the first entry: an allowance of 1 permits the original entry and one return after exit. It does not count the original entry as that return.

A repeat Entry while the holder is still inside is not a valid exit-and-return sequence. Scan an actual departure in Exit mode so both admission rules and capacity remain accurate.

Capacity and zone access

Zones can have their own capacities and ticket-type access. Entry to a full zone is refused until an exit frees capacity. A holder eligible for the event is not automatically eligible for every restricted zone.

Use the assigned zone consistently at entry and exit. The venue dashboard distinguishes current occupancy from cumulative attendance. See Venue operations.

Benefits and entitlements

Use Benefits at a configured benefit point, such as lunch collection, merchandise pickup or a VIP service. Scan the ticket to check that it includes the relevant benefit, is within the permitted conditions and has uses remaining.

The result records an allowed redemption. A second presentation cannot redeem a one-use benefit again. Benefits governed by event presence require the holder to be inside; an exited holder must complete an allowed re-entry before redeeming. A benefit scan does not itself admit the holder or override an entry refusal.

For setup and examples, see Re-entry and benefits.

Ticket lookup

Use Ticket lookup when a code cannot be read. Enter the ticket code or holder email, then choose the correct ticket if several match. Lookup follows the current event, scan point and Entry, Exit or Benefits mode. The same admission and entitlement rules apply.

Keep the ticket's identity and event visible while resolving a guest enquiry. Use accreditation lookup for booking and collection work rather than repeatedly attempting entry.

Sales and accreditation

The Tickets area supports selling, issuing and complimentary tickets. Accreditation Desk handles registration lookup, ticket collection, walk-ins and ticket printing. Ticket checkout can collect payment and print admission QR codes with a receipt.

See Ticket sales and accreditation for the complete desk workflow, and Venue operations for schedules, participants and oversight.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Configure event, scan point and zone.
  2. Use continuous camera or external-scanner input.
  3. Record Entry and read allowed or refused results.
  4. Move to the next holder without another confirmation tap.
  5. Use the result’s dismiss control.
  6. Record Exit and apply re-entry allowances correctly.
  7. Apply duplicate, cancelled, wrong-event, zone and capacity rules.
  8. Use Ticket lookup by code or email.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Event Info Center — supporting guide

Keep staff informed about current and upcoming sessions.

What you will learn

  • Select the event and information-desk layout
  • Read sessions happening now
  • Review sessions beginning soon
  • Use session details to guide attendees
  • Read operational figures in context
  • Refresh and coordinate schedule changes

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Overview and event selection

The event workspace keeps staff tools under one selected event. Review its title and dates before opening admission or ticket actions. Use event selection when changing assignments; changing a business location and changing an event are separate choices.

Info Center

Info shows sessions happening now and starting soon, with operational figures to help staff answer attendee questions. Refresh when checking a programme change. Use it at an information desk or while directing people to their next session.

Schedule

Schedule brings session timing and details together. Browse the event programme and use the available date, track or session filters. Authorized staff can maintain sessions through the event tools. Event-wide programme and configuration work can also be managed from web administration.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Select the event and information-desk layout.
  2. Read sessions happening now.
  3. Review sessions beginning soon.
  4. Use session details to guide attendees.
  5. Read operational figures in context.
  6. Refresh and coordinate schedule changes.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Event attendance, occupancy and capacity — supporting guide

Read attendance and current zone load correctly.

What you will learn

  • Open the selected event’s dashboard
  • Read tickets and cumulative unique check-ins
  • Review scan attempts and denials
  • Read current zone occupancy and configured capacity
  • Understand how Exit releases capacity and re-entry affects attendance
  • Review session and participant figures
  • Use the correct metric for venue decisions

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Statistics and occupancy

Stats opens the live event dashboard. Review ticket totals, unique check-ins, scan activity, denials, sessions and participant counts. Zone occupancy shows how many holders are currently inside a zone and its configured capacity.

FigureMeaning
TicketsTicket records for the event
Unique check-insHolders admitted over the reporting period
Scan attempts and denialsActivity at scanning points, including refused presentations
Current occupancyEntries less recorded exits for the zone
CapacityThe configured limit used for admission decisions

A person who attended and later left remains part of attendance history but no longer occupies a place inside. Always use current occupancy for decisions about available space.

Management and activity

Use Manage for event details and the actions available to your role, including publication. Maintain event setup, ticket types, zones and stations in web administration when preparing the operation. Review activity and admission history when resolving a ticket or movement enquiry.

Keep the ticket desk, door and benefit counters coordinated through the same event records. See Access and benefits setup.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Open the selected event’s dashboard.
  2. Read tickets and cumulative unique check-ins.
  3. Review scan attempts and denials.
  4. Read current zone occupancy and configured capacity.
  5. Understand how Exit releases capacity and re-entry affects attendance.
  6. Review session and participant figures.
  7. Use the correct metric for venue decisions.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Accreditation, walk-ins and ticket printing — supporting guide

Find registrations, fulfill ticket collection, register walk-ins and print admission tickets.

What you will learn

  • Select the event and accreditation desk
  • Look up the holder’s email or booking reference
  • Apply desk ticket-type and walk-in rules
  • Fulfill collection and use the current admission QR
  • Register an eligible walk-in with attendee details
  • Open Ticket / print and print a readable admission code
  • Keep printing, handover and entrance scanning as separate actions

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event. Configure the payment provider and compatible hardware used in the lesson before beginning collection or printing.

Prepare the desk

Administrators configure ticket types, pricing, sale availability, capacity, event zones and accreditation points. Each desk can have its own ticket-type and walk-in rules. Assign the device's business location, configure payment methods and connect its ticket printer.

Collect an existing booking

  1. Open Accreditation Desk and select the desk or General accreditation.
  2. Search by holder email or the booking or confirmation reference.
  3. Identify the correct ticket in the results.
  4. Use Fulfill for ticket handover. Fulfilment rotates the admission QR for the collected ticket.
  5. Open Ticket / print, review the holder and type, then Print ticket.

Give the holder the current issued code. A previously replaced code should not be used for admission. Ticket printing and accreditation handover do not replace an entrance scan.

Register a walk-in

Choose Walk-in Registration at a desk that permits walk-ins. Select an eligible ticket type and enter the attendee's name and contact details. Complete the registration and use the resulting ticket's print action. Paid attendance should follow the configured sale and payment workflow.

Desk restrictions control which ticket types can be handled and whether walk-ins are available. Choose the proper desk for the attendee's allocation.

Ticket printing

Connect the receipt or thermal printer under Devices and choose its paper width. Use the ticket print action to print the QR at a readable size with the holder and event information. Keep the print window open until you choose Close, allowing additional copies where appropriate.

Multiple paper copies of one ticket represent the same admission credential; they do not create additional entries or benefit uses. Reprinting a receipt does not collect another payment.

Continue with Event scanning and Printers.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Select the event and accreditation desk.
  2. Look up the holder’s email or booking reference.
  3. Apply desk ticket-type and walk-in rules.
  4. Fulfill collection and use the current admission QR.
  5. Register an eligible walk-in with attendee details.
  6. Open Ticket / print and print a readable admission code.
  7. Keep printing, handover and entrance scanning as separate actions.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Ticket sales, issuing and complimentary admission — supporting guide

Sell, issue or comp tickets, collect payment and print distinct admission QR codes with a receipt.

What you will learn

  • Read the event ticket list and summary counts
  • Choose an available ticket type and quantity
  • Sell tickets through Ticket checkout
  • Collect cash or a configured card payment
  • Resume an unfinished sale
  • Issue tickets or record a comp reason
  • Print distinct ticket QR codes and the receipt
  • Use the order and ticket records for later enquiries

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event. Configure the payment provider and compatible hardware used in the lesson before beginning collection or printing.

Prepare the desk

Administrators configure ticket types, pricing, sale availability, capacity, event zones and accreditation points. Each desk can have its own ticket-type and walk-in rules. Assign the device's business location, configure payment methods and connect its ticket printer.

Sell tickets

  1. Open Tickets → Sell and choose an available ticket type.
  2. Set the quantity and holder details.
  3. Choose the payment method and continue to Ticket checkout.
  4. Review the ticket lines, currency and amount before collecting payment.
  5. Complete payment using the selected cash, card or other available method.
  6. Choose Print tickets & receipt to give the holder admission codes and their payment record.

A multi-ticket sale produces distinct tickets. Hand each holder the appropriate code. A printed ticket contains a scannable QR code and a readable reference for lookup; the reference text alone is not the barcode.

An unfinished ticket checkout is saved on the device. Use Resume checkout to continue that sale, or the available cancellation action to abandon it. Review an existing payment result before initiating another collection.

Issue and complimentary tickets

Issue creates a ticket using the selected type and holder details. Comp records a complimentary ticket with a reason, such as a speaker or VIP allocation. Use the appropriate action for the organization's ticketing policy; ticket issuing and collecting payment are separate responsibilities.

Search or refresh the ticket list to inspect holder details and status. The summary counts describe issued ticket records; use current occupancy when deciding how many people are inside.

Ticket printing

Connect the receipt or thermal printer under Devices and choose its paper width. Use the ticket print action to print the QR at a readable size with the holder and event information. Keep the print window open until you choose Close, allowing additional copies where appropriate.

Multiple paper copies of one ticket represent the same admission credential; they do not create additional entries or benefit uses. Reprinting a receipt does not collect another payment.

Continue with Event scanning and Printers.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Read the event ticket list and summary counts.
  2. Choose an available ticket type and quantity.
  3. Sell tickets through Ticket checkout.
  4. Collect cash or a configured card payment.
  5. Resume an unfinished sale.
  6. Issue tickets or record a comp reason.
  7. Print distinct ticket QR codes and the receipt.
  8. Use the order and ticket records for later enquiries.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Event schedules and sessions — supporting guide

Find the event's sessions during operations.

What you will learn

  • Open the selected event’s programme
  • Browse session timing, days and tracks
  • Read session details
  • Maintain sessions with the appropriate role
  • Coordinate event-wide changes in web administration
  • Use Info Center for now-and-next guidance

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Info Center

Info shows sessions happening now and starting soon, with operational figures to help staff answer attendee questions. Refresh when checking a programme change. Use it at an information desk or while directing people to their next session.

Schedule

Schedule brings session timing and details together. Browse the event programme and use the available date, track or session filters. Authorized staff can maintain sessions through the event tools. Event-wide programme and configuration work can also be managed from web administration.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Open the selected event’s programme.
  2. Browse session timing, days and tracks.
  3. Read session details.
  4. Maintain sessions with the appropriate role.
  5. Coordinate event-wide changes in web administration.
  6. Use Info Center for now-and-next guidance.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Event participants and staff — supporting guide

Manage speakers, exhibitors, staff and other participants.

What you will learn

  • Filter people by participant type
  • Add a speaker, exhibitor or staff participant
  • Inspect their profile and role
  • Confirm invited participants
  • Change a role or remove a participant when appropriate
  • Distinguish participant registration from admission entitlement

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

People

The People view organizes event participants such as speakers, exhibitors and staff. Filter by participant type, inspect the record, add a participant, confirm an invitation or change a role where your permissions allow. Remove a participant only when they should no longer be listed.

Participant records and admission tickets have different purposes. Adding a speaker or exhibitor does not by itself replace the ticket or credential policy for entering a controlled zone.

Management and activity

Use Manage for event details and the actions available to your role, including publication. Maintain event setup, ticket types, zones and stations in web administration when preparing the operation. Review activity and admission history when resolving a ticket or movement enquiry.

Keep the ticket desk, door and benefit counters coordinated through the same event records. See Access and benefits setup.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Filter people by participant type.
  2. Add a speaker, exhibitor or staff participant.
  3. Inspect their profile and role.
  4. Confirm invited participants.
  5. Change a role or remove a participant when appropriate.
  6. Distinguish participant registration from admission entitlement.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Event setup, access rules and benefits — supporting guide

Coordinate event setup, zone access, re-entry allowances, accreditation and ticket benefits.

What you will learn

  • Review event details and publication controls
  • Configure zones and capacity in event administration
  • Configure entrance, exit and benefit scan points
  • Set single-entry and re-entry ticket policies
  • Count re-entry as returns after the first admission
  • Configure lunch or other benefits and use limits
  • Require current presence for inside-event benefits
  • Configure accreditation-point restrictions and walk-in rules

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Configure access centrally so every event device applies the same rules. In the event's web administration, define ticket types, zones, scan points, accreditation points and benefits. Staff select those definitions on mobile.

Zones and scan points

A zone identifies a controlled area, such as a hall, exhibition floor or VIP lounge. Set its capacity and the ticket types allowed to enter. A scan point identifies where a device operates and supplies the relevant zone and access conditions.

Use explicit names—Main Gate, Hall Exit, VIP Entrance, Lunch Desk—so staff can choose the right station. Review the event and point shown on each scanning device before opening the venue.

Re-entry policy

Choose whether each ticket type permits re-entry. Where an allowance is set, it counts returns after the initial admission.

PolicyExample sequence
Single entryEntry, then Exit; no return admission
One re-entryEntry → Exit → Entry; another return is beyond the allowance
Additional re-entriesEach permitted return follows an Exit and consumes another allowance

Apply any configured date, time and zone restrictions along with that policy. A duplicate scan while already inside is not a return visit. Staff must record exits to keep movement history and occupancy meaningful.

Benefit counters

Define the benefits included with a ticket type, their use limits and conditions. Configure a benefit scan point to accept the relevant benefit identifiers, then select Benefits on its mobile scanner.

For a lunch entitlement, associate Lunch with the eligible ticket types and the Lunch Desk point. An allowed scan records the redemption. A one-use lunch cannot be redeemed twice, including from another device.

Presence-dependent benefits require the holder to be inside the event. For example, a guest who has exited and cannot re-enter is not entitled to redeem an inside-event meal by bypassing the entrance and going directly to the counter.

Accreditation rules

Accreditation points can restrict ticket types and walk-in registration. Assign the appropriate point at each collection desk. Registration, fulfilment, printing, admission and benefit redemption are separate actions with separate records.

Staff procedure

  • At entrances, use Entry and follow the admission result.
  • At exits, use Exit so a later return and current occupancy can be evaluated correctly.
  • At benefit counters, use Benefits and follow the redemption result.
  • At the ticket desk, use accreditation lookup and ticket actions for holder enquiries.

See Event scanning, Ticket desk and Venue operations.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Review event details and publication controls.
  2. Configure zones and capacity in event administration.
  3. Configure entrance, exit and benefit scan points.
  4. Set single-entry and re-entry ticket policies.
  5. Count re-entry as returns after the first admission.
  6. Configure lunch or other benefits and use limits.
  7. Require current presence for inside-event benefits.
  8. Configure accreditation-point restrictions and walk-in rules.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Meetings and field appointments — supporting guide

Create a meeting from the mobile scheduling screen.

What you will learn

  • Open Book from the enabled apps
  • Choose the meeting context and participants
  • Set the date, time and available details
  • Review the request before submitting
  • Follow the resulting meeting record
  • Create the next task or customer follow-up

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Meetings

Book opens the meeting scheduler. Set the meeting details, date, time, participants and context offered by the booking flow. Review the details before submitting and follow the resulting meeting record.

For a field visit, keep the contact, meeting and follow-up task aligned so another staff member can continue the work.

A field-agent routine

  1. Open the assigned lead or find the contact before a visit.
  2. Read the customer journey and previous communication.
  3. Call or message through the business channel.
  4. Update the lead and capture the agreed next step.
  5. Create a task or meeting for follow-up.
  6. Use the relevant workflow for work handed to another team.

Continue with Communications, Prep and workflows and Workspaces.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Open Book from the enabled apps.
  2. Choose the meeting context and participants.
  3. Set the date, time and available details.
  4. Review the request before submitting.
  5. Follow the resulting meeting record.
  6. Create the next task or customer follow-up.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Workspaces, rooms and shared activity — supporting guide

Inspect shared work and members from the phone.

What you will learn

  • Open a workspace and inspect membership
  • Filter the feed by room and category
  • Read human and AI-authored activity
  • Select the composer’s workspace or room destination
  • Post an update and follow shared work
  • Use workspace context when coordinating an approval or handoff

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Workspaces

Choose a workspace to read its shared activity and context. Workspace cards show its name, description, membership and recent activity. Inside a workspace, use room and category filters to narrow the feed.

Activity items identify their author, including AI-authored work, and show the message, related room and reply information. Open the members control to see the people participating. Use the shared context when coordinating a handoff or reviewing work before a decision.

To post an update, choose the workspace or room first and check the composer destination. Enter the message and tap Send. A room post goes to that room; the combined workspace feed gives a wider view of activity. Use refresh to follow new work.

Workspace membership and broader setup are managed through the organization's workspace administration.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Open a workspace and inspect membership.
  2. Filter the feed by room and category.
  3. Read human and AI-authored activity.
  4. Select the composer’s workspace or room destination.
  5. Post an update and follow shared work.
  6. Use workspace context when coordinating an approval or handoff.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile AI employee supervision — supporting guide

Give work and manage an employee's operating state.

What you will learn

  • Read employee role, state and idle reason
  • Give a task with clear context and constraints
  • Switch on, pause or restart the employee
  • Read credit and daily-spend information
  • Use authorized credit and spend controls
  • Follow output in Workspaces
  • Manage broader employee setup through web administration

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

AI employees

The AI employee list shows each employee's role, operating state, activity and spending information. Read an idle or paused reason before deciding the next action.

ActionPurpose
Give workSubmit a task with the outcome and context the employee needs
Switch onStart an employee that is ready to operate
PauseStop further work while you review or change direction
RestartRestart the employee's operating session
Add creditAdjust the available credit through the authorized control
Reset today's spendReset the displayed daily-spend accounting control where permitted

Write work requests with a clear goal, relevant records and any constraints. Follow the output in the employee's shared work context. Use web administration for employee creation, knowledge, tools, access and broader operating policies.

A mobile supervision routine

  1. Review shared context in the workspace.
  2. Check the AI employee's state and current assignment.
  3. Give a specific task or pause work that needs review.
  4. Decide any resulting request under For me.
  5. Return to the workspace and decision history to follow the outcome.

Use CRM tasks for ordinary assigned work and Prep and workflows for staged operational work.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Read employee role, state and idle reason.
  2. Give a task with clear context and constraints.
  3. Switch on, pause or restart the employee.
  4. Read credit and daily-spend information.
  5. Use authorized credit and spend controls.
  6. Follow output in Workspaces.
  7. Manage broader employee setup through web administration.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.

Appmint Mobile Approvals, requests and decision history — supporting guide

Review a request, submit a decision and inspect the recorded result.

What you will learn

  • Read For me and inspect the requested action
  • Approve or reject with an optional note
  • Confirm the decision and follow its status
  • Track your requests under Mine
  • Withdraw an eligible request
  • Read Alerts and mark notifications read
  • Review completed decisions under Done

Before you begin

Sign in to the intended organization and enable the required apps under Features (apps & menus). Use a staff role with access to the workflow and select the relevant business location or event.

Approvals

The approval workspace separates your responsibilities:

  • For me holds requests awaiting your decision.
  • Mine tracks requests you submitted, with withdrawal available for eligible requests.
  • Alerts holds approval-related notifications and a Mark all read action.
  • Done provides completed decision history.

Open a request and read the action, summary and relevant details. Choose Approve or Reject, add an optional note and confirm. The decision is recorded against that request. Check its resulting status before treating the work as authorized or completed.

For a request you no longer need, use Withdraw from Mine and confirm. An approval decision is separate from the eventual outcome of the action that follows it.

A mobile supervision routine

  1. Review shared context in the workspace.
  2. Check the AI employee's state and current assignment.
  3. Give a specific task or pause work that needs review.
  4. Decide any resulting request under For me.
  5. Return to the workspace and decision history to follow the outcome.

Use CRM tasks for ordinary assigned work and Prep and workflows for staged operational work.

Practical walkthrough

Work through the following sequence with a sample business scenario. Keep the same customer, order, ticket or work record throughout the lesson.

  1. Read For me and inspect the requested action.
  2. Approve or reject with an optional note.
  3. Confirm the decision and follow its status.
  4. Track your requests under Mine.
  5. Withdraw an eligible request.
  6. Read Alerts and mark notifications read.
  7. Review completed decisions under Done.

Continue learning

Open the product guide or return to the Appmint Mobile course catalogue.