Culture and Talent
A day in the life of Dwolla’s community experience manager
- Bobby Godbersen is building the team that supports Dwolla's growing list of White Label API customers.
- His day takes us from Slack messages, to solving a crisis, and finishing off with a volleyball match.
Account support managers of fintech companies are the unsung heroes of finance. Sales reps may get the glory, and executives get to speak at all sorts of events (like Money’16), but when things go south and servers go down, all eyes are on the support team. Bobby Godbersen is the Community Experience Manager of Dwolla, a Des Moines-based digital payment network provider. He works under the VP Sales and Strategy, and is in charge of building the team that supports their growing list of White Label API customers. Here is a glimpse into a day of his life: 4:45 a.m.: Daily alarm goes off and it’s time to hit the gym. 6:15 a.m.: Fix breakfast (2 eggs and toast) while I watch SportsCenter to get my morning update on the world of sports. 7:15 a.m.: After eating breakfast and getting ready, it’s time to walk to work. I throw on my headphones and hit shuffle on Spotify’s TGIF playlist (because every workday should feel like Friday). 7:30 a.m.: Enter office (Yep, only 15 minute walk to work. Love Des Moines!) and it’s time to catch up on items I missed from the evening. Check Slack for outstanding messages. Slack, a real-time messaging platform, allows us to create individual communication channels for our White Label customers. 8:30 a.m.: Sync with the account management team to get up-to-speed on any emerging issues with our White Label customers. I also use this time to get an update on our recently-signed customers who are going through the on-boarding and review process for their applications. 9:00 a.m.: Initial call with a newly signed White Label customer. These kick-off calls introduce a new customer to their assigned support team and it’s our chance to learn about their business model, payment needs, and objectives in their words. This particular partner is building an application to make consumer saving easier by telling Dwolla’s White Label API to transfer small amounts of funds each week from an individual’s checking account to a savings account. Our bank transfer API automates a lot of the traditional functions and requirements of bank transfers for customers, so we really act like advisors trying to maximize the efficiency of an integration. It’s also why I’m joined by Spencer, our lead dev support engineer. More on him later. 9:30 a.m.: I race over to Cleveland (rooms at Dwolla are named after individuals depicted on U.S. currency) for another customer meeting. This one is technical and Spencer leads. He discusses best practices and answers questions about the APIs core endpoints: create an account, link a funding source, create transaction, and webhooks (for real-time notifications from the webserver). 10:00 a.m.: Time to catch my breath and go through emails. I have three more calls this afternoon and need to make sure everything is in order for each. 11:00 a.m.: Weekly meeting with the marketing/communication and sales team. Marcom is looking to feature one of our recent customers in a case study. Sales provides feedback on what type of featured use-case would resonate with prospective customers. We select the ideal candidate for the case study and I schedule a call the following day to introduce our marcom team. 11:45 a.m.: Spencer gets an SOS from a developer on the customer’s dedicated Slack channel. They plan to push integration live to production tomorrow for their own internal stakeholders, but something isn’t right. We schedule a call for 12:00 p.m. 11:50 a.m.: Spencer and I meet quickly with our liaison to the Platform Team to cover our bases (i.e. “assume you’re wrong first”). Nothing is out of order on our end. All services are up. 12:00 p.m.: Jump on call. Spencer and lead developer for White Label customer identify the problem quickly. It’s on their end, but it’s not an easy fix. Spencer has time to stay on and work through. 12:15 p.m.: Lunch time. I eat at my desk while going through my twitter feed and any priority emails. 1:00 p.m.: Weekly cross-functional meeting with sales, legal, product and compliance teams. Product discusses the updates to the new Dwolla Dashboard & Admin, a new tool that helps partners to manage customers, view transaction details and discover business trends. Based on customer feedback the product team rolled-out advanced filters for searching and new graphs for viewing transaction volume between customers within an application. 2:00 p.m.: I join Ben S., an in-house information security expert, for an infosec review of one of our new White Label customers. The session offers a 360° assessment of the customer’s entire platform, and focuses on vulnerability, encryption, authentication, and application security. 2:30 p.m.: I have 30 minutes before my next call. Time for a quick foosball match. It helps clear my mind while also keeping my skills sharp for our weekly Friday tournaments. 3:00 p.m.: Outside of the on-going support, we try to carve out some time with willing customers to get product feedback. Today, we’re speaking with a customer discussing their desire for Same Day ACH. The conversation focuses on their business processes and whether or not Same Day will achieve their objective (to improve customer relations). It does. 3:30 p.m.: Check emails. Prepare for 4pm meeting, by compiling notes from recent customer interactions. 4:00 p.m.: In the last step of the review process before an integration goes live, we conduct a quick audit and demo of a customer’s integration for compliance purposes. In addition to ensuring compliance, we love to see the end result of a customer’s integration with our API. Integrations can last as little as a week to as long as a few months, depending on the needs and resources of the customer. This particular client took two weeks and one developer to complete a fairly complicated integration. 5:00 p.m.: Prior to kickoff meetings, an account manager and technical integration lead will meet with the sales rep to discuss the use-case of a newly signed customer. Sales leads this meeting by providing an overview of the customer’s business, integration details, and desired timeline for launching on White Label. Today, I’m sitting in with Megan, one of our new account managers, as she goes through this process with Sales for the 3rd time. 5:40 p.m.: Check the Slack channels and emails one last time. No fires. I walk home and change for my weekly sand volleyball match. 7:30 p.m.: Our work team, “The Sand Dwollas”, lacks experience but makes up for it with enthusiasm and a unique sense of humor. I return home with a win under my belt as well as several grains of sand. 9:00 p.m.: My sleep schedule has been described as that of a 90-year-old nightowl. I’m asleep by 9:30 pm.