I used to read trip codes out loud over the phone. That lasted about three trips before I swore it off entirely. There is something uniquely maddening about spelling a six-character code to someone at highway speed, watching the confusion unfold in real time as “B” becomes “D” and “M” becomes “N” and suddenly you are both frustrated before the drive even starts.
Now I screenshot the code the second I create a trip. Every single time. The screenshot lives in my camera roll, ready to be dropped into any chat, any platform, no thinking required.
That said, a screenshot is just one approach. Depending on your group, the situation, and what phones everyone is carrying, there are faster ways to handle this. Some are obvious, some are less so, and at least one will probably change how you share codes going forward.
The Copy-Paste Default
When you create a trip in Konvoyage, the code shows up on screen. Tap it to copy. Paste it into your group chat.
Straightforward as that sounds, there is one thing that catches people off guard. Some phones tack on an invisible trailing space when you tap to copy text. The person on the other end pastes the code into the join field, and it fails because of a phantom space character sitting at the end. I have watched this confuse people who are perfectly tech-savvy, because you cannot see the extra space just by looking at the message. If someone says “the code isn’t working,” that trailing space is the first thing to check. Tell them to manually type the characters they see instead of pasting, and it usually resolves instantly.
One more thing about group chats: send the code as its own standalone message. Do not bury it inside a paragraph of logistics about where to meet and what time to leave. People scroll fast, and a wall of text gets skimmed. A code sitting by itself gets noticed.
I once sent a code buried in the middle of a long message about meeting times, parking, and who was bringing the cooler. Three out of four people missed it entirely and texted me separately asking for the code. I had literally sent it. It was right there in the message. But nobody reads a six-line text with the same attention they give a standalone code. Now I always send the logistics in one message and the code by itself immediately after, and nobody has missed it since.
Why Not Just Hit Share?
This is the move I reach for most often now. The share button in the app opens your phone’s native share sheet, which means you can fire the trip code through whatever channel makes sense, whether that is iMessage, WhatsApp, Signal, SMS, Slack, or anything else installed on your phone. The share sheet usually formats the message with a bit of context, something like “Join my trip on Konvoyage” along with the code and a link. That extra framing matters when you are sending it to someone who has never used the app before, because a random code with no explanation just looks like spam.
I am still figuring out the fastest workflow when my group has a mix of iPhones and Androids. The share sheet behaves differently on each platform, and getting Konvoyage working across both adds a small layer of “which messaging app does everyone actually check.” For now, I default to regular SMS for mixed groups. It is the lowest common denominator, and it works.
When You Have to Say It Out Loud
Sometimes there is no way around a phone call. Someone is already driving, or they do not have the group chat, or their phone is acting up.
Verbal code-sharing is the worst method. But occasionally it is the only one.
Use the NATO phonetic alphabet. I know it feels dramatic for a short code, but it eliminates every ambiguity in one pass. “Bravo, Kilo, Seven, Mike, Two, Papa” takes a few extra seconds compared to just rattling off the letters, but you will not spend the next minute going back and forth with “wait, was that a B or a D?” The letters that trip people up most over phone calls are B and D, M and N, S and F, P and T. NATO phonetics exist specifically because those pairs are nearly identical through a phone speaker. After the person hears the code, have them read it back to you before they type it in. That confirmation loop catches mistakes before they become frustration.
I learned this the embarrassing way on a trip to Big Bend a couple of years ago. My friend was already on the road, no data signal, and I had to call him with the trip code. I just read the letters casually. He typed what he heard. It did not work. I read them again, slower. Still did not work. We went back and forth for almost five minutes, him getting increasingly annoyed while merging onto the interstate, before I finally realized he had been typing an “F” where I was saying “S.” Five minutes of frustration over a single consonant. I switched to NATO after that and have never had the problem again.
There is also the question of background noise. If the other person is in a car with the windows down, or at a rest stop with trucks idling nearby, even clear enunciation gets swallowed. NATO helps, but so does timing. Call when they are parked, not when they are driving at seventy miles per hour with the radio on. A thirty-second wait for them to pull into a gas station saves you both the aggravation of repeating yourself four times into wind noise.
Just Show Your Screen
If your group is standing together before splitting into separate cars, skip all of the above. Just hold up your phone and let everyone look at the screen. No copying, no pasting, no spelling anything out.
Some apps offer QR codes for this exact scenario, which is even faster since people just point their camera and the code auto-fills. But the screen-show approach works perfectly fine for small groups and requires zero setup. The catch is obvious: this only works when everyone is physically in the same place. If people are joining from different starting points, you are back to digital sharing.
What Actually Matters
The trip code is short on purpose. Sharing it should match that energy.
Honestly, the method matters less than the habit. Most of the time I just screenshot the code and drop it in the group chat, and that covers ninety percent of situations. If someone is not in the chat, I hit share and send it directly. Phone calls are a last resort, but NATO phonetics have saved me enough times that I do not even think about it anymore. The point is that once you find the thing that works for your group, you stop deliberating. It becomes automatic. I have not had a code-sharing failure in over a year, and the only reason is that I stopped trying to be clever about it and just picked one approach and stuck with it.