Crossplay makes ASA bigger, but it also creates more ways to misunderstand an order. Console, crossplay and server type must be part of the scope, not an afterthought.
What to confirm first
Before talking price, confirm the platform and cluster. Small Tribes, console-only, crossplay and unofficial settings can change delivery method, availability and timing. The seller needs to know where the character is and where the item or service must land.
- Platform: Xbox, PlayStation, PC or crossplay context.
- Server type and cluster name.
- Map and character location.
- Whether voice, text or ticket instructions are required.
Delivery differences
Crossplay orders fail when people assume everyone sees the same server list or can transfer the same way. For dinos, resources and kits, confirm if the handoff is direct. For carries, confirm whether the buyer character can join the run on that cluster.
- Searchable server name or number.
- Transfer cooldown and upload status.
- Safe meeting point and inventory space.
- Proof after delivery.
Common mistakes
The most common mistake is mentioning console too late. If the seller priced or planned for a different cluster, the order can delay or become impossible. Put it in the first message.
- No platform in ticket title or first message.
- Wrong server type.
- Buyer character cannot reach delivery map.
When a service makes sense
Use custom services when platform or crossplay details affect delivery. Layeh's ticket flow keeps platform, cluster and character details visible before checkout or manual payment.