Kathleen F.

I’ve been in Software my entire career selling it designing it buying it — all of it. I know engineers love something new,, something shiny. That’s where the fun is . what I’m saying is this —-fix what is broken now —- credits credits credit credits. We don’t have to talk about this anymore. I think I’ve been pretty clear and I think you’ve been really generous with your responses and I truly appreciate them. Please don’t interpret my remarks is anything more than that. Cheers. Kathleen

Well, to summarize: Tables chew up credits — 1. for unresolved bugs (Sculpt commands that don’t work)) and 2. for automatic running of columns in a table. Bugs happen. But credit use is a usability feature that should be under the control of the engineering team. And it’s expensive to me and it’s time consuming to contact support. And 3) system slow downs. I ran into all three today. And all the above take my time to figure out, address, contact support.

Yes a human. I certainly don't want a bot to answer. These are issue with the Clay system. Not a bot.

i was going to post something on LinkedIn how good the extension is. It still does some good work. even tho' it's discontinued. Look forward to updated version. Thanks again!

awesome video!!!! and I used the clay extension it for some good purposes already. let me take a peek here. thanks LouisArturo.

start at second 30. I highlighted the send to email link.

really all i need is will i get the scraped list and when.... here's a zoom clip link to the my process https://zoom.us/clips/share/V1NDIS8LQWW7e-lSf_arDg Passcode: R@.R6JG0

NOt a table//// didn't get that far. This is the page I'm trying to scrape https://connect.summitna.com/8_0/explore/session-speakers.cfm#/alpha/