Critical Solicit Codes in GC GO November 13, 2026 01:25 Updated Welcome! Solicit codes tell your team how, and whether, a constituent wants to be contacted: "Do Not Call," "No Email," "Anonymous," "Contact Through Spouse," and whatever else your shop tracks. Critical Solicit Codes let you pick the codes that matter most to each team and put them front and center: when a gift officer opens a constituent with one of those codes, GC GO shows a red warning banner before they reach out.This guide covers what critical solicit codes are, how to set them up for each team, where the banner appears, and who sees it.What this feature doesEvery constituent can carry any number of solicit codes, usually imported from your CRM. Most are useful background. A few are must-knows: the ones that should stop a gift officer before they pick up the phone or hit send.Critical Solicit Codes let a GC GO admin flag those must-know codes team by team. When a gift officer opens a constituent who has one of their team's critical codes, they see a banner like this at the top of the page:Critical Solicit Code: Do Not Call, No Email Consider these preferences before interacting with the constituent.The banner lists every critical code that applies, separated by commas.Good to know: The banner is a heads-up, not a lock. It doesn't block calls, emails, or tasks. It just makes sure the officer sees the constituent's preferences before deciding what to do next.Why it's set by teamDifferent teams care about different codes. Your Major Gifts team may need to know about "Contact Through Principal Gifts Only," while your Annual Giving team needs to see "No Phonathon." Setting critical codes per team means each officer sees the warnings that are relevant to their work, without a wall of red on every record.Where the setting livesFrom the GC GO menu, open School Settings and click Teams. Each team on the page has its own list of critical solicit codes, set from the team's edit panel.You'll need the GC GO school-settings permission to see this page. It usually comes with the GC Gift Officer Admin role.Add critical solicit codes to a teamGo to School Settings → Teams.Click to edit an existing team, or create a New Team.In the panel that opens, find the Critical Solicit Codes field.Start typing the name of a solicit code. Matching codes from your school's list will appear.Select each code you want to flag. Selected codes show as chips in the field.Click Save.From that point on, every gift officer on that team will see the warning banner on constituents who carry any of the selected codes.Remove a critical solicit codeOpen the team again, remove the code's chip from the Critical Solicit Codes field, and click Save. Officers on that team will stop seeing the banner for that code. The code itself stays on the constituent's record; you're only changing whether it's flagged as critical for that team.Tip: You can only pick from solicit codes that already exist at your school. If a code you need isn't showing up, it hasn't been imported yet. See Importing Constituent — Solicit Codes with the GC Data Importer to bring it in.Where gift officers see the bannerThe red Critical Solicit Code banner shows up in two places:The constituent record. Right below the record's header and tabs, on every tab (Overview, Giving, Contact Reports, and so on).Tasks. At the top of a task for that constituent, above the task card, including cadence tasks. That way officers see it right when they're about to call, email, or text.If the constituent is also marked deceased, a second red banner appears just below it saying "Constituent is deceased."Who sees whatThe banner is personal to the person looking at the record. GC GO checks two things:Which team the viewing gift officer belongs to.Whether the constituent has any of that team's critical solicit codes.Only the codes that match on both counts appear. So two officers on different teams can open the same constituent and see different banners, or one may see a banner and the other may not.A few things that follow from that:Officers without a team won't see the banner. If someone isn't assigned to a team, there's no list of critical codes to check against. Assign them a team in Staff Management to turn it on.Officers don't need to own the constituent. The banner shows for anyone on the team who opens the record, whether or not the constituent is in their portfolio.Moving an officer to a new team changes what they see. Their banner will follow the new team's critical codes right away.A few tipsKeep the list short. The banner works because it's rare. Flag the codes that should change what an officer does, not every code on file.Talk with each team first. Ask team leads which preferences they've been burned by in the past. Those are your critical codes.Keep your solicit codes current. The banner is only as accurate as the codes on the record. Re-import solicit codes regularly so changes in your CRM make it into GC GO.Review when teams change. If you add a new team, remember to set its critical codes. New teams start with none.TroubleshootingI don't see "Teams" in School Settings. The page requires the GC GO school-settings permission, which usually comes with the GC Gift Officer Admin role. Ask your GiveCampus admin to confirm you have it.A code I want to flag doesn't come up when I search. Only solicit codes that already exist at your school can be selected. Import the code onto at least one constituent with the Constituent — Solicit Codes data type, then search again.A gift officer says they don't see the banner on a constituent who has the code. Check three things: the officer is assigned to a team, that team has the code selected under Critical Solicit Codes, and the code is actually on this constituent's record in GC GO (not just in your CRM).Two officers see different banners on the same constituent. That's expected. Each officer sees only the critical codes for their own team.Does the banner stop someone from calling or emailing? No. It's a visual warning only. Officers can still complete tasks and reach out. It's there so they make that choice with the constituent's preferences in front of them.I removed a critical code from a team. Is it gone from the constituent? No. Removing it from the team only stops the banner for that team. The solicit code stays on the constituent's record.Need a hand?If something here doesn't match what you're seeing, your GiveCampus admin can confirm your school's team setup and permissions, and the GiveCampus team is always happy to help you decide which codes deserve the red banner.Now go make sure every outreach starts on the right foot. 🚩 Comments 0 comments Article is closed for comments.
Comments
0 comments
Article is closed for comments.