[{"data":1,"prerenderedAt":243},["ShallowReactive",2],{"marketing-blog-blog\u002Fone-brand-every-surface-guests-touch":3,"marketing-blog-related-blog\u002Fone-brand-every-surface-guests-touch":224},{"id":4,"title":5,"author":6,"body":7,"category":202,"date":203,"description":204,"draft":205,"extension":206,"image":207,"imageAlt":208,"imageCredit":209,"imageCreditUrl":210,"meta":211,"navigation":212,"path":213,"readTime":214,"seo":215,"stem":216,"tags":217,"__hash__":223},"blog\u002Fblog\u002Fone-brand-every-surface-guests-touch.md","One brand, every surface guests touch","The CheckInHub team",{"type":8,"value":9,"toc":193},"minimark",[10,14,17,22,25,28,44,47,53,57,60,149,152,156,159,168,172,175,183,187,190],[11,12,13],"p",{},"Count the number of times a guest meets your brand before they ever hear a speaker. The invitation email. The registration page they fill in. The confirmation that lands in their inbox. The reminder a week out. The QR pass on their phone. The kiosk or desk they check in at. The badge that goes round their neck. That is at least seven distinct surfaces, and at most events at least one of them is wearing somebody else's branding — usually the software vendor's. The guest notices, even if they could not say what bothered them. The event felt slightly cobbled together, and the seam was the part you outsourced.",[11,15,16],{},"Brand consistency at an event is not vanity. It is the difference between an experience that feels deliberately yours and one that feels assembled from whatever tools were to hand. Every surface a guest touches is either reinforcing that this is your event or quietly undermining it.",[18,19,21],"h2",{"id":20},"where-the-seams-usually-show","Where the seams usually show",[11,23,24],{},"The branding breaks tend to appear at the handoffs — the moments where your own materials give way to a platform's defaults. These are easy to miss because you, the organiser, have seen them so many times they have become invisible. The guest, seeing them for the first time, notices the change in voice immediately.",[11,26,27],{},"The usual offenders:",[29,30,31,35,38,41],"ul",{},[32,33,34],"li",{},"A confirmation email that arrives from a generic noreply address with a vendor's footer.",[32,36,37],{},"A registration page on a URL that is plainly not yours, with someone else's logo in the corner.",[32,39,40],{},"A check-in screen at the door that announces the software rather than the event.",[32,42,43],{},"A QR pass that looks like it came from a different organisation entirely.",[11,45,46],{},"Each one is small. Together they tell the guest that the front-of-house experience was rented, not made. And the front of house is precisely where you most want the event to feel like yours, because it is the first thing the guest meets.",[48,49,50],"blockquote",{},[11,51,52],{},"A guest should never be able to tell which parts of your event you built and which you bought.",[18,54,56],{"id":55},"the-surfaces-and-who-owns-the-brand-on-each","The surfaces, and who owns the brand on each",[11,58,59],{},"It helps to lay out every surface a guest touches and ask, plainly, whose brand is on it. Most organisers find at least two surprises in this exercise.",[61,62,63,79],"table",{},[64,65,66],"thead",{},[67,68,69,73,76],"tr",{},[70,71,72],"th",{},"Surface",[70,74,75],{},"Should show",[70,77,78],{},"Often shows",[80,81,82,94,105,116,127,138],"tbody",{},[67,83,84,88,91],{},[85,86,87],"td",{},"Invitation email",[85,89,90],{},"Your name, your domain",[85,92,93],{},"A shared noreply address",[67,95,96,99,102],{},[85,97,98],{},"Registration page",[85,100,101],{},"Your brand, your URL",[85,103,104],{},"The vendor's subdomain",[67,106,107,110,113],{},[85,108,109],{},"Confirmation and reminders",[85,111,112],{},"Your voice and logo",[85,114,115],{},"Generic platform template",[67,117,118,121,124],{},[85,119,120],{},"QR pass",[85,122,123],{},"Your event's identity",[85,125,126],{},"Default styling",[67,128,129,132,135],{},[85,130,131],{},"Check-in screen",[85,133,134],{},"Your event",[85,136,137],{},"The software's name",[67,139,140,143,146],{},[85,141,142],{},"Badge or lanyard",[85,144,145],{},"Your brand",[85,147,148],{},"Often fine, sometimes not",[11,150,151],{},"The exercise is not really about the table. It is about the right-hand column — the surfaces where someone else's brand has crept in without anyone deciding it should. Every row where the middle and right columns disagree is a small inconsistency the guest absorbs.",[18,153,155],{"id":154},"email-is-the-surface-that-leaks-most","Email is the surface that leaks most",[11,157,158],{},"Of all the surfaces, email is where the brand most often slips, because it feels like infrastructure rather than design. A confirmation from a shared noreply address does three things, none of them good: it looks impersonal, it is easy to mistake for spam, and it quietly tells the guest that you did not think this part was worth owning. An email that comes from your own domain, in your own voice, does the opposite — it lands in the inbox as plainly yours.",[11,160,161,162,167],{},"This matters more than its size suggests, because email is often the first surface a guest touches and the one they return to when they need details. ",[163,164,166],"a",{"href":165},"\u002Fblog\u002Femails-that-come-from-you-not-a-shared-noreply","Emails that come from you, not a shared noreply"," covers why sending from your own domain changes how those messages are received, both by the guest and by their spam filter.",[18,169,171],{"id":170},"your-domain-on-the-door","Your domain on the door",[11,173,174],{},"The most visible seam, after email, is the URL. A registration page on someone else's subdomain is a small thing that does real work against you. It looks less trustworthy, it is harder for guests to recognise as legitimate, and it advertises the platform at the exact moment you want to advertise the event. Putting your own domain on the registration and check-in pages closes that seam entirely. The guest sees your address, your brand, your event — and the software disappears, which is exactly where software belongs.",[11,176,177,178,182],{},"For organisers running events for clients, this goes further still. A white-label setup means the guest never sees the platform at all, only the host's brand, end to end. ",[163,179,181],{"href":180},"\u002Fblog\u002Fwhite-label-check-in-for-agencies","White-label check-in for agencies"," covers that case, where the consistency is not just nice but contractual.",[18,184,186],{"id":185},"consistency-as-a-quiet-signal","Consistency as a quiet signal",[11,188,189],{},"What all this adds up to is a single, quiet signal sent across every surface: this event was made on purpose, by people who cared about the details. The guest will not consciously register that the email, the page and the door all matched. They will register the absence of the small jarring moments that tell them otherwise. Coherence is felt as confidence; inconsistency is felt as carelessness, even when the event itself is excellent.",[11,191,192],{},"Walk every surface a guest touches, from the first email to the badge, and check whose brand is on each. Close the seams — your domain on the pages, your voice in the emails, your event on the door — and the whole thing reads as considered. CheckInHub puts your brand on every one of those surfaces by default, from custom domains to branded emails to themed check-in screens, so the guest meets your event everywhere and the software nowhere. One brand, every surface, is not a luxury finish. It is the difference between an event that feels yours and one that feels borrowed.",{"title":194,"searchDepth":195,"depth":195,"links":196},"",2,[197,198,199,200,201],{"id":20,"depth":195,"text":21},{"id":55,"depth":195,"text":56},{"id":154,"depth":195,"text":155},{"id":170,"depth":195,"text":171},{"id":185,"depth":195,"text":186},"Branding & domains","2025-09-12","A guest meets your brand a dozen times before the keynote. When every one of those surfaces matches, the event feels considered rather than cobbled.",false,"md","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1671376354112-6de3d08b97af?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop","An ID card attached to a lanyard","jim","https:\u002F\u002Funsplash.com\u002F@skill01?utm_source=checkinhub&utm_medium=referral",{},true,"\u002Fblog\u002Fone-brand-every-surface-guests-touch",5,{"title":5,"description":204},"blog\u002Fone-brand-every-surface-guests-touch",[218,219,220,221,222],"branding","white-label","custom domains","consistency","guest experience","nUOq2nmOfv-l5-TKuR6TKW9T8Q82KythKAt-Z7RNdQ0",[225,232,237],{"to":226,"title":227,"description":228,"date":229,"category":202,"image":230,"readTime":231},"\u002Fblog\u002Fyour-brand-at-every-touchpoint","Your brand, at every touchpoint","Guests should never feel like they have left your event to use someone else's software. Here is how white-labelling works across CheckInHub, and why we made it the default.","2026-06-19","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1561489413-985b06da5bee?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",3,{"to":165,"title":166,"description":233,"date":234,"category":202,"image":235,"readTime":236},"A noreply sender quietly undermines your event emails. Here is why sending from your own brand and domain changes how guests respond.","2025-10-03","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1564456008877-3317cd4c0a8f?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",6,{"to":238,"title":239,"description":240,"date":241,"category":202,"image":242,"readTime":236},"\u002Fblog\u002Fwhy-we-made-branding-the-default-not-an-upgrade","Why we made branding the default, not an upgrade","Most platforms charge extra to remove their logo from your event. We decided your brand on your door should be the standard, not a paid add-on.","2025-09-26","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1613347761493-4060c969cd28?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",1782495582058]