Questions

DEPARTMNT builds TapTech: Tags, the physical product; the Portal, the fan facing page; and Core, the client dashboard. See What DEPARTMNT is.

Send a brief to hello@departmnt.xyz, and you get a reply within a working day. See Submitting a brief.

Partly, today: self serve is a beta for selected Base, Studio and Label clients from Q4 2026, with the full platform going to selected clients in 2027. Every other deployment is managed by DEPARTMNT. See How a project runs.

Self serve lets a brand set up Core, choose tags, build its Portal and launch it without us. Agency and Network projects are account managed instead: brief, scope, proposal. See the two routes.

Only if you tell them what happens when they do: on a retail floor with staff and signage, 74% of taps became a registration, and on a garment tag with nobody next to it, 41% became an entry. Where nothing explained the tap, most sessions ended inside a minute, so the on ramp matters more than the tag. See What makes a deployment work.

For reaching a lot of people, a QR code is the better tool and it is cheaper: anyone can scan it from across a room, or from a screenshot. A tap needs a phone at a specific object, which makes it proof of presence rather than proof of interest. See How it works.

Ten: Sticker sheet, On metal sticker, Card, Wristband, Mini CD, Resin tag and Garment tag, with Metal card, Lanyard and Key tag coming soon. Each comes off the shelf, customised, or as a bespoke build made for the object. See Tags.

Not everywhere: metal is the usual problem, and a tag behind thick timber gave trouble once too, though both are solved with a shielded on metal inlay, which costs more. Otherwise TapTech has run on an enclosed retail floor, across a city and in an open festival field. See surfaces on Tags.

Both tag tiers authenticate the tag. Standard is NXP NTAG213. Advance, NXP NTAG424 DNA, adds encrypted cryptographic authentication on every tap. See Tags and authentication.

Every recent iPhone and Android phone reads a tag with no app. The phone is unlocked, held to the tag, and the page opens. See How it works.

Switch it off, or point it somewhere new, from Core. Nothing on the tag needs to change. See How a tap is checked.

Yes, a tag can be programmed to open anything. The Portal is what unlocks the full journey, and the full picture in Core. See a tag without a Portal.

Nothing, unless someone decides: a tag stays live, and on one deployment page views were still landing four months after the activation ended. Pointing those tags at the next drop is a database change rather than a print run, but it only works if it is somebody's job. See What makes a deployment work and the end of a campaign.

No. The Portal is served at [brand].departmnt.io, and push notifications are web push, with no app. See How it works.

Yes, through eleven brand tokens, with legibility checked before publish. See theming on Portal.

Yes. Push is web push, with no app, on Android, desktop, and iPhone or iPad once the Portal is added to the Home Screen (iOS 16.4 and later). See Push notifications.

The brand's own card asks first, and the phone's prompt appears only after a yes. Turning off takes two taps in Settings, and applies on all of a person's devices. See push consent rules.

The brand is the controller and owns its data. DEPARTMNT is the processor, under contract. See who controls the data.

Yes: every tier exports your records, so they can go into the tools you already use. Label adds scheduled exports. The API, with webhooks, is for Agency and Network only, and is not for sale until it ships. The rest is set out in Tiers. See Core.

Your tags, Portals and campaigns, a Fans view with a record per fan, and analytics as consent filtered aggregates. Exports are consent filtered and watermarked. See Core.

The software is a subscription on one of five tiers, and hardware is priced per unit, with breaks at higher quantities. Prices are published on Tiers, and the calculator gives a total for tags and a tier. See How pricing works.

Any one of these can move you up, and the highest one sets the tier: more Portals or campaigns live at once, a second brand or client, a bigger team, more active tags or contacts, numbers further back, selling tickets or taking payment, running a membership, records into your own tools, reporting you hand to a client, or an estate of venues or stores. See What moves you up a tier.

Nothing stops working. We tell you, and you choose an add on or the next tier, so a Portal never goes dark in the middle of an event. See How pricing works.

In the shop, or from the calculator on Pricing on the website. You select tags, customise them, choose a quantity, order, then configure them in Core. The plan is billed in Core, the tags in the shop. See Ordering tags.

Stock lead times run from 1 week for sticker sheets and garment tags to 4 to 6 weeks for metal cards. Custom lead times and minimums are quoted against your brief. See timelines.

Yes: the Ticketing module sells tickets through Core Commerce and checks them at the door through Core Access. Fans get an event pass in their hub that shows valid, used or transferred. See Ticketing.

Yes: organisers set a per buyer cap, counted across account and payment method. A cap is not an automated purchase ban. See Core Commerce.

One scan per ticket is enforced at the database, and door checks work offline. At the door a human decides, and we never refuse entry automatically. See the door.

Which tag was tapped, when, and the category of device. It is a record of presence, not of a person, until someone chooses to sign up. See what a tap records.

Yes: delete your own account from the account drawer at any time, or ask the brand. See your rights.