--000000000000786d2606199c9e12 Content-Type: multipart/alternative; boundary="000000000000786d2506199c9e11" --000000000000786d2506199c9e11 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Here=E2=80=99s what I=E2=80=99m thinking=E2=80=A6 On Wed, May 29, 2024 at 2:36=E2=80=AFPM Phil Chanda wrote: > Graphically, we can add whatever image you want. As noted previously, th= e > current image is a placeholder. > > If you send me the design of what the answer is, I can see how we can add > it to the web page. > > On Wed, May 29, 2024 at 2:27=E2=80=AFPM Ray Smale = wrote: > >> Monica - I'm not a fan that once I've entered all my information on this >> form I still don't get the answer to the quiz and I now have a download = to >> do to get it. >> I think it's very bait and switchy, not very customer friendly. >> [image: Screenshot (1254).png] >> >> It leaves a bad taste - I'm wondering how many more of these hurdles do = I >> need to keep jumping through. >> Is there a way we can avoid this? >> At a minimum a big 13 needs to be in the blue box preceded by "The Answe= r >> is:" >> Ideally there's also a graphic that shows how you get to 13 - so a green >> outline for the small boxes, red for med, blue for the large ones - Phil >> that's a graphical challenge for you pls. >> With that, then the question is where do we route people from here, >> having given them the answer. >> Thanks for your thoughts, >> Ray >> >> On Wed, May 29, 2024 at 10:20=E2=80=AFAM Phil Chanda >> wrote: >> >>> This is the way it mapped in Salesforce API at the moment and how it wa= s >>> originally built. Monica, can speak to this in more detail but this is >>> tied to "API Field Name: CallerName__c" >>> >>> On Wed, May 29, 2024 at 10:17=E2=80=AFAM Ray Smale wrote: >>> >>>> Can we pls break the name field into: >>>> First Name >>>> Last Name >>>> ? >>>> >>>> On Tue, May 28, 2024 at 5:53=E2=80=AFPM Ray Smale wrote: >>>> >>>>> Got it. Thanks >>>>> >>>>> On Tue, May 28, 2024 at 5:48=E2=80=AFPM Monica Schmidt >>>> monica.schmidt@thekey.com> wrote: >>>>> >>>>>> Ray, >>>>>> We will be leveraging our existing connection to Salesforce for this >>>>>> form, so we need all four fields to be populated for automated and m= anual >>>>>> follow up processes. >>>>>> >>>>>> On Tue, May 28, 2024 at 1:03=E2=80=AFPM Timothy Thomas wrote: >>>>>> >>>>>>> Looks great. Nice work Phil. >>>>>>> >>>>>>> On Tue, May 28, 2024 at 1:56=E2=80=AFPM Phil Chanda >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Ray, >>>>>>>> >>>>>>>> We need all fields so that it can be entered into Salesforce/Pardo= t >>>>>>>> as a lead. I'll let Monica S chime in on the tracking & automatio= n aspect >>>>>>>> with regards to Pardot & Salesforce. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Phil >>>>>>>> >>>>>>>> On Tue, May 28, 2024 at 1:22=E2=80=AFPM Ray Smale >>>>>>>> wrote: >>>>>>>> >>>>>>>>> I love it! >>>>>>>>> Great work. >>>>>>>>> Tim - Do we need post code? We can get it when we call them back. >>>>>>>>> >>>>>